StoaIn build

Let the merchant edit their storefront without letting them near checkout

Catalog, cart, checkout and orders as a real API, with a visual builder over only the storefront a customer looks at — scoped so a merchant can rewrite their homepage and still cannot reach checkout. In build.

In build — tell us what you need and we will say honestly how close it is.

Stoa — end to end
  1. Commerce API
  2. Storefront surface
  3. Visual builder
  4. Merchant edits safely

Why this exists

Merchants get a storefront they cannot touch, or a page builder with no real commerce underneath it. The split between what is safe to edit and what is not is the whole design problem.

Catalog, cart, checkout and orders on a Laravel API, with a visual builder over the parts of the storefront customers see — so a merchant can change their own homepage without a developer and without breaking checkout.

What it does

Everything Stoa handles for you.

  • Visual site builder

    WordPress-style editing of the storefront surface, scoped so it cannot reach the parts that take money.

  • Real commerce core

    Catalog, cart, checkout, orders and settings as a proper API rather than a theme with a database behind it.

  • Separate admin

    Merchant administration is its own surface, not a plugin bolted onto the shop.

What you get

Concretely, what lands.

Not adjectives — the things that exist afterwards that did not exist before.

  • A visual site builder over the storefront surface, scoped so it cannot reach the parts that take money.
  • Catalog, cart, checkout, orders and settings as a proper Laravel API rather than a theme with a database behind it.
  • Merchant administration as its own surface, not a plugin bolted onto the shop.

How it works

From nothing to working.

  1. Commerce first

    Catalog, cart, checkout and orders are built as an API. Everything visual sits on top of that, which is the opposite of how a theme-plus-plugins store is assembled.

  2. Draw the line

    The storefront surface — what a customer looks at — is editable. The checkout path is not. Where that line falls is the whole design problem, and it is decided once rather than per merchant.

  3. Hand over the builder

    WordPress-style editing of the surface, so changing a headline stops being a developer ticket.

  4. Administer separately

    Merchant admin is its own surface with its own permissions.

Who it's for

Built for these people.

If you are not one of them, we will say so rather than sell you a seat.

  • Merchants who keep paying a developer to change a headline
  • Agencies deploying storefronts they do not want to maintain forever

Pricing

Two ways to buy it.

Stoa can run on our infrastructure under your brand, or on yours. The difference is who gets the call when it breaks.

ManagedWe run it.
$129/mo

per branded store · $2,500 setup

  • Deployed under your brand, on your domain
  • We host, monitor, patch and update it
  • A failure at 2am is ours to fix, not yours to diagnose
  • Monthly — cancel when it stops being worth it
Start managed
Self-hostedYou run it.
$3,500 once

+ $900/yr updates and support

  • Runs on your own infrastructure, inside your own network
  • One production instance, plus as many staging and local copies as you need
  • Yearly renewal covers updates, security patches and support
  • Source code is not included in either tier
Get a quote

Before you ask

The questions that come up.

  • Stoa is in build. If you are an agency deploying storefronts you do not want to maintain forever, now is a good time to tell us what you need from it.

  • The builder is scoped so it cannot reach the parts that take money. That constraint is the product; if we relaxed it, this would be a page builder like every other one.

  • If those fit, use them. Stoa exists for deployments where you need the commerce core to be your own API and the editing surface to be genuinely safe to hand over.

  • A managed branded store with a setup fee, or a one-time self-hosted licence with annual updates and support. Prices are on this page.

Be first on Stoa.

A few lines is enough. A senior engineer reads it and replies within one business day — and says straight away if it isn't a fit.

Or email us directly at contact@caffinix.com.

Or email contact@caffinix.com. We sign a mutual NDA before scoping if you need one.

Built on·Laravel 12 · Next.js 15 · Postgres

← All products
Stoa
In build
Early access →