Open source · Pre-release

Never replatform again.

OrbCommerce is four products around your shop: catalog, search, content and checkout. Replace the part that holds you back. Add the next when you are ready. Nothing moves twice.

Runs in your own Cloudflare account · EU by default

nordgrat.shop
NordgratPacksJacketsBoots
backpack 30 l under €150
1

New this autumn

Alpin 30
Alpin 30
€139.95In stock
Föhn Hardshell
Föhn Hardshell
€179.00In stock
Grat Mid
Grat Mid
€159.95Few left

Your shop today.

  • OrbCartCharged once. Whatever happens.idempotent by key
  • OrbCatalogMillions of products. One grid.one Postgres, one API
  • OrbSearchEvery result explains itself.rules, synonyms, pins
  • OrbPageA card never points at nothing.resolved, never copied

The family

Four products. Each with a job of its own.

Own runtime, own data, own deploy. OrbCatalog, OrbCart and OrbSearch each stand alone. OrbPage builds on the catalog.

OrbCart

Checkout that asks your systems.

Your ERP keeps the last word on price and stock. VAT for every EU country, the payment providers you already use, one order.

Explore OrbCart
Order summary 2 items
Grat 22Slate · 22 l
€99.95
HeadlampBlack
€46.99
Shipping€5.90
VAT 19 % included€24.40
Total€152.84
Pay €152.84

Order #10476 · awaiting payment

OrbSearch

Search that knows what shoppers mean.

It understands the query, follows your rules and explains every result.

Explore OrbSearch
OrbCatalog

A product database editors enjoy.

Design product types without a developer. Keep millions of products in one grid. Your PIM syncs in, one way.

Explore OrbCatalog
ProductsSaved
NameSKUStockStatusAlpin 30NG-ALP-3042LiveGrat 22NG-GRT-2218LiveFels 45NG-FLS-457DraftFöhn rain jacketNG-FHN-RT31ChangedHeadlampNG-STL-0164Live
OrbPage

Pages around live products.

Campaigns, categories and stories built from your storefront's own parts. Products are resolved, never copied.

Explore OrbPage
Autumn on the ridgeLive
  1. Hero
  2. Story
  3. Product card
  4. Newsletter
Autumn on the ridgeLight packs for long days above the tree line.
Alpin 30
€119.95live from catalog
Subscribe

How it fits

Start with the one that hurts. Add the next without moving twice.

Each product meets your systems through a seam. When the next product joins, the seam points at it.

How it works

The price lives in your ERP. So we ask it.

Nothing is copied into a second system that has to be kept in step. Every truth has one owner, and it is asked at the moment it matters.

one purchaseNordgrat
  1. shopperadds Alpin 30 to the bag
  2. orbcartoffers("ALPIN-30") → your ERP
  3. your erp€139.95 · in stock
  4. orbcartquote signed
  5. shopperpays by card
  6. orbcartpaid · charged once
  • No copies.offers() at quote time
  • No sync jobs.one owner for every truth
  • Nothing stale.prices read when they are needed

The search index is the one copy. It follows the change feed with its own cursor.

The admin

One admin for all four. Made for people who live in it.

Install one product and it is that product's admin. Install four and they share one sidebar, one search and one sign-in.

admin.nordgrat.shop/products/alpin-30
Alpin 30NG-ALP-30
LiveSavedPublish

Product

What shoppers need to recognise and trust it.

Name
Alpin 30
SKU
NG-ALP-30
Barcode
4260512830306
Description
A 30-litre pack for long days above the tree line, with a back that breathes and a lid that opens wide.

A few sentences on what makes it worth buying.

Pictures

The first one leads the product page.

Drop pictures here

Pricing

Base price
EUR139.95
Offer price
EUR0.00

Leave empty to sell at the base price.

  • Instant.

    An edit shows at once and saves behind it.

  • Undo, not "Are you sure?"

    Change a hundred thousand products. Take it back after.

  • One sign-in.

    Every product trusts the same team session.

For developers

Small APIs that read like prose.

One typed client per product. Install only yours.

product.ts
import { catalog } from "@orbcatalog/client";
import type { Nordgrat } from "./catalog.types";

const nordgrat = catalog<Nordgrat>({ url: "https://catalog.nordgrat.shop" });

const route = await nordgrat.route("alpin-30", { locale: "en" });
if (route.status !== "found" || route.kind !== "product") throw notFound();

const [found, offers] = await Promise.all([
  nordgrat.product(route.ref, { locale: "en" }), // base data, cached long
  nordgrat.offers(route.ref, { channel: "en" }), // price and stock, cached seconds
]);
  • Typed from your schema

    Types come from your live schema with one command.

  • Described in OpenAPI

    Every route, for people and for agents.

  • Signed, one way

    Events and calls between products carry one signature format.

$npm i @orbcatalog/client

Pre-release. The packages are not on npm yet.

For agents

Agents prepare. People decide.

An agent can find, draft and propose. Whatever changes your shop waits for a person.

  • Their own tools.mcp, per product
  • One approval, one change.expires after 15 minutes
  • Publishing is a second yes.prices and stock are not tools
AI Chat Nordgrat admin

Draft the English description for Alpin 30 from the German one.

  1. find_products"Alpin 30"
  2. read_draftNG-ALP-30
  3. edit_draftdescription.en
Proposal · Edit draft expires in 15 min
Alpin 30 · Description (English)
A 30-litre pack for long days above the tree line, with a back that breathes and a lid that opens wide.
RejectApprove

Approved by Mara · draft saved

Proposal · Publish expires in 15 min

Alpin 30 goes live in 3 languages.

RejectApprove

Scale

Built for the first sale. And for the first ten minutes of a campaign.

We build and test against four shops.

150orders a minuteThe campaign.The last piece is sold exactly once.

Targets we design and test for. Not benchmark results.

Why it holds

The last piece is held before it is paid for.reserve · commit · release
Every cart is its own small computer.one Durable Object per cart
A retry is never a second order.Idempotency-Key
Answered at the edge.lifetime first, purge second

Under the hood

Nothing exotic. Parts you already trust.

TypeScript end to end, on web standards.

  • Your storefrontany framework · typed clients · react parts
  • The four productscloudflare workers · orbsearch on your server
  • Statedurable objects · postgres per merchant · r2
  • Your systemserp · pim · payment providers
  • strict typescript
  • zod
  • openapi 3.2
  • rfc 9457 problem details
  • cloudevents
  • rfc 9421 signatures
  • es256
  • better auth
  • oauth + pkce
  • mcp
  • ucp
  • stored in the eu
  • vat for 27 eu countries
  • stripe
  • adyen
  • mollie
  • payone
  • paypal
  • amazon pay

Pre-release. Some payment methods still wait for their sandbox proof.

Plainly

A shop builderAn ERPA CMS for everythingA hosted service Four parts for the shop you already run.

Four ways to start

  1. Shop platformMove everything in.

  2. Composable suiteWire everything first.

  3. Point solutionsOne piece. Loose ends.

  4. OrbCommerceOne part. Then the next.

No themes, no app store, no years in production. Pre-release, and it needs a developer.

What changes

For the one who signs. And the ones who live with it.

If you decide

You stop buying migrations.

If you build

You read the API in an afternoon.

If you edit every day

The grid keeps up with you.

Cost

A bill you can read. Before you talk to anyone.

No licence fee. No share of your revenue. No paid plan.

Estimate for a small shop: a few coffees a month, from the vendors' price lists.

NORDGRAT · NOVEMBER

  • Cloudflare Workersby use
  • Postgresyour provider
  • Payment feesyour provider
  • OrbCommerce licence€0.00
  • Share of revenue0 %
  • Sales callsnone

YOU PAY FOR WHAT RUNS

Questions

Worth asking before you start.

Do we have to use all four?

No. OrbCatalog, OrbCart and OrbSearch each work alone, with their own runtime, data and deploy. OrbPage builds on OrbCatalog. Most merchants start with the one that hurts.

We already run an ERP, a PIM and a shop.

Keep them. OrbCart asks your ERP for price and stock through one function you write. OrbCatalog takes a one-way sync from your PIM. Your storefront keeps rendering and calls an API where it used to call the old part.

What if our ERP is slow or down?

Then there is no quote, and the shopper is told so. OrbCart waits three seconds, keeps the bag and never invents a price.

How live is live?

An offer is good for fifteen minutes unless your ERP says otherwise, and you can cancel it sooner. The price is checked again at payment. If it changed, nothing is charged.

Where does it run, and where is our data?

The Workers run in your own Cloudflare account, the database at the Postgres provider you choose, OrbSearch's engine on your servers. Data is stored in the EU by default. Edge services and your payment provider may process it elsewhere.

Is it open source?

OrbCart and OrbPage carry the Apache 2.0 licence, OrbSearch's clients MIT. OrbCatalog's licence is decided before its first public release. The repository is not public yet.

Can we go live today?

No. Everything here is pre-release. Nothing is on npm, and deploying is still manual. Try the demo shop, read the docs and follow each product's status page.

Start with one. Grow into all.

Put something in the demo shop's bag and pay for it. Then read how it would ask your systems.