The enterprise funnel platform for scale
One data layer under pages, checkout, CRM and the call center, with an API, a CLI and a server-side runtime for the engineers who will own it.
Your pages should not live in a black box
A marketing platform usually means your site lives in someone else's database, reachable only through their editor. Here the whole project is a folder your pipeline can push.
Checkout built for volume
Charges route by weight across your NMI MIDs, with rule filters and caps. Cards go straight to your gateway: the API never returns a card number or CVV.
- Route by product, card brand and ticket size
- Order bumps and one-click upsells
- Recovery calls from the built-in call center
Where low-code runs out, keep going
Backend scripts run real JavaScript per request in a sandbox. The funnel graph routes visitors by rule before a page renders.
- Wall-clock cap, capped outbound HTTP, a key-value store
- Inbound webhooks from gateways land as events
- Any automation can call an endpoint you run
Your pages are files
Open the project in the editor your team uses and let the pipeline ship it.
Nothing changes without a record
For the people who answer for the account six months from now.
Change history
Who changed what, field by field. Secrets redacted before writing.
Revisions and rollback
Pages, funnels and automations restore in one click.
Per-project permissions
Access on one client inherits nothing on another.
Two-factor, org-wide
TOTP per user, or mandatory across the organisation.
GDPR erasure
Cascades through every analytics store, with an audit row kept.
No card data stored
Cards go to your gateway. The API returns brand and last four only.
From first call to signed MSA
Priced per account above the top published tier.
Book a 30-minute call
Walk through your funnels, gateways and call center setup.
Try it on a real funnel
A 14-day trial, with the API and CLI included.
Agree terms
One monthly number, with the MSA and DPA negotiated with your legal team.
Enterprise funnel platform FAQ
Can our engineers manage the stack like code?
Yes. Pages live as files in a folder you edit in VS Code or Cursor and can keep in your own git repository. The CLI takes an API key, prints JSON, supports a dry run and returns documented exit codes, so a deploy job can push pages unattended and fail the build when something is wrong.
Can we run our own code, or is this low-code only?
You can run real code. Backend scripts execute server-side JavaScript per request in a sandboxed runtime with a wall-clock cap, capped outbound HTTP and a per-project key-value store. Beyond that there is a documented REST API across pages, funnels, products, orders, customers, CRM, automations and analytics, and any automation can make an outbound HTTP call to a system you run.
Can we see who changed what?
Yes. Every project keeps a change history recording the user, the record, the action and the timestamp, with field-level before and after values. Secrets are redacted before anything is written to it. Pages, components, funnels and automations also keep their own revisions with the author attached, and restore in one click.
How do we control who can do what?
Organisation roles set what a user can reach, and each user carries their own permissions on each project, so an account manager on one client does not inherit anything on another. TOTP two-factor can be switched on for an individual or made mandatory across the whole organisation, and API keys are issued per device and revoked individually.
Can you delete a customer on request?
Yes. Deleting a customer by email cascades the erasure through every analytics store and the identity graph rather than only the primary database, and leaves an audit row behind as evidence that it ran.
What happens above 500K page views a month?
Traffic above the top published tier is priced per account rather than by the tier table, so you get one predictable monthly number instead of overage surprises. MSAs and DPAs are negotiated with your legal team rather than handed over as take it or leave it.