Skip to content

Platform

One system instead of four

Elara One runs your shop, your CRM, your automation and your inbox on one customer record, with one admin for your team and one API for your website.

Get startedBook a demo

Architecture

Everything orbits one customer

Your website and your team come in through two doors. Behind them, every module reads and writes the same customer record, in a database that belongs to your store alone.

Read the diagram as a list
  1. Your storefronts. Your own website, one of our starters (Next.js, Nuxt or Astro) or your own apps and scripts.
  2. The API lock. Browser calls are accepted only from your registered websites; server calls must carry your secret.
  3. One API. One REST API at /api/v1 for the catalogue, cart, checkout, forms, chat and the CRM.
  4. Your team and two-step sign-in. Every staff account signs in with two steps, then works in one admin for the shop, the CRM and the inbox.
  5. The engine. Commerce, CRM, Email, Inbox, Automation and Forms, all writing to one customer record. Analytics is coming soon.
  6. One database per store. Your store’s data, search index, cache and media are kept apart from every other store.
  7. Payments. Stripe and PayPal on your own accounts. No fees on your sales, and card details never reach Elara One.

  1. 01

    Two doors in

    Your storefronts use the API. Your team uses the admin. Both are locked: registered websites and a server secret for one, two-step sign-in for the other.

  2. 02

    Modules, not tools

    Commerce, CRM, Forms, Automation, Inbox and Email are parts of one engine, so nothing has to be copied between them.

  3. 03

    One record at the centre

    An order, a form, a text message and a task all land on the same customer, the moment they happen.

  4. 04

    Your data, your money

    Each store has its own database. Payments go to your own Stripe or PayPal account, with no fees on your sales.

One customer record

At the centre, one customer

Ada asked for a quote on Monday, had a text back within minutes and bought on Wednesday. In Elara One that is one person with one timeline, not three half-records in three tools.

  1. Sent the “Quote request” formForms · lead created
  2. Lead routed to Grace HopperCRM · routing rule
  3. Grace replied by SMSInbox · six minutes later
  4. Order #1048 paid, £157.00Commerce · Stripe
  5. Order confirmation sentEmail · as Hearth & Oak
  6. Task: call about a trade accountTasks · due today

Duplicates are found by email, phone, name and company, or postcode, and merged side by side with consent carried over.

One admin

One admin, built for the keyboard

Orders, customers, leads, flows and conversations live in one admin with one sign-in. Your team learns one place, and every list works the same way.

Press⌘Kanywhere in the admin

  • Command menu

    Press ⌘K and type a name, an order number or a setting. Jump straight there.

  • Keyboard first

    J and K move through every list, Enter opens, ⌘S saves. No hunting for buttons.

  • Staff permissions

    Roles and fine-grained permissions. Record access by owner, team or everyone, and sensitive fields only for the people allowed.

  • Two-step sign-in

    Required for every staff account. Passkeys, “remember this device” for up to 30 days and an email when a new device signs in.

One API

One API for every part of it

The same base URL and the same key serve your catalogue, checkout, forms and CRM. One way to authenticate, one error format, one set of rules to learn.

  • One key per storeYour public key identifies the store; your secret stays on your server.
  • Locked to your websitesBrowser calls work only from websites you register. Keys rotate with a 7-day overlap.
  • Exactly-once ordersSend an Idempotency-Key and a retried checkout never places a second order.
  • Money you can trustPrices are whole pence, never floats: £89.00 is 8900.
  • Signed webhooksCRM changes are signed with HMAC-SHA256, retried, and logged with “Send again”.
Explore the API
curl -G https://api.elaraone.app/api/v1/products \
  -H "X-Tenant-Key: pk_live_…" \
  -H "X-Tenant-Secret: $ELARAONE_TENANT_SECRET" \
  -d "filter[collection]=lighting" \
  -d "include=variants.prices"
Money, everywhere
"price": {
  "amount": 8900,
  "currency": "GBP",
  "formatted": "£89.00"
}
Errors, everywhere
"error": {
  "code": "ORIGIN_NOT_ALLOWED",
  "message": "This website is not
    registered for the store."
}

One base URL and one key for every module. The merchant API adds keys with only the permissions you grant.

Before and after

Five tools, or one

Most growing shops end up with a shop, an email tool, a CRM, an inbox and something to connect them. Here is what changes when it is one system.

  • The customer

    Separate tools

    A copy in every tool, matched by email address when the sync works.

    Elara One

    One record with every order, form, message, email and task.

  • Signing in

    Separate tools

    A login per tool, each with its own security settings to check.

    Elara One

    One admin. Two-step sign-in is required for every staff account.

  • Automation

    Separate tools

    Triggers hop between tools through webhooks and a connector.

    Elara One

    17 triggers and 12 actions working on the same data, with nothing in between.

  • When something breaks

    Separate tools

    Find which sync failed, then fix the data in two places.

    Elara One

    There is no sync to fail. Every module reads the same record.

  • Your data

    Separate tools

    Spread across several vendors, each with its own export.

    Elara One

    Your store’s own database. Export contacts to CSV, or read everything through the API.

  • Paying for it

    Separate tools

    A subscription per tool, each priced its own way.

    Elara One

    One plan for the whole system. No fees on your sales.

Modules and plans

Pay for the side you use

Choose Elara One Leads or Elara One Commerce. Commerce includes everything in Leads, plus the shop.

FAQ

Questions, answered

Something else? Book a demo and ask the people who build it.

Do I have to use every module?
No. Every store has the CRM, forms, automation and email. Add the shop with a Commerce plan, and the inbox depending on your plan. Modules you do not use stay out of your way in the admin.
Can I keep my current website?
Yes. Your website talks to Elara One through the API, so you can keep your design and your domain. If you would rather not build one, start from one of our storefront starters.
What does “one customer record” mean in practice?
Orders, form submissions, text messages, chat, emails and tasks all appear on one timeline for each person. When the same person turns up twice, Elara One flags the duplicate and you merge them side by side.
Can I bring my contacts from another CRM?
Yes. The guided CSV import maps your columns, runs a dry run first and handles marketing consent. There is also a direct import from HubSpot.
Do you take a cut of my sales?
No. Payments go straight to your own Stripe or PayPal account. We charge a plan price, never a fee on your sales.
Where is my data kept?
Your store runs in London, on UK servers, in a database of its own. Encrypted backups are kept in the EU. Card details stay with Stripe and PayPal and never reach Elara One.
Can my developer connect other tools?
Yes. The merchant API uses keys with only the permissions you grant, CRM changes are sent as signed webhooks, and any flow can call a webhook of its own.
What is coming next?
Analytics, WhatsApp in the inbox and AI voice calls are built and coming soon. Deals and pipelines, wholesale and campaigns are on the roadmap.

Bring your business into one orbit

Get started today, or book a demo and we will walk you through your shop, your leads and your inbox in one admin.

Get startedBook a demo