Drop your plans, your docs and your AI key into a conversational checkout your buyers actually finish. Hosted on your domain, settled on your Stripe.
your stripe · your ai key · your domain · your data
1 afternoon
from signup to a live checkout
100%
of offers validated server-side
2 providers
Anthropic or OpenAI — your key
0 card details
ever touch our servers
Live demo
This is a real eeze checkout for Nimbus, a fictional analytics SaaS. Ask it hard questions, haggle for the annual discount, take it all the way to payment.
Built for SaaS teams like
Product
Three systems working together: grounded answers, guardrailed offers, and analytics that turn every buyer question into product intelligence.
Point eeze at one plain-text URL and your checkout learns your product cold. Security posture, refund policy, plan differences — buyers get a straight answer, cited from the exact section it came from, without leaving the purchase.
You write the rules: which promo codes exist, whether an annual switch can be offered, what the ceiling is. The model proposes; the server disposes. An offer outside your rules isn't just discouraged — it's rejected before it reaches the order.
SAVE20 — 20% off first year
promo code · max 1 per order
Switch to annual
2 months free · any plan
Free-form discounts
assistant-invented offers
✓ offer SAVE20 accepted — matched rule, applied server-side
✕ offer "50% off forever" rejected — no matching rule
Every buyer question is captured. The ones your knowledge base couldn't answer are clustered into ranked knowledge gaps — so the question that cost you a sale on Tuesday is answered for everyone by Wednesday.
Completion
68% +9pts
Questions
1,284 30 days
Knowledge gaps
7 3 new
“Does the API have webhooks?”
“Is there an on-prem option?”
Everything included
Buyers ask anything — pricing, security, refunds — and get grounded answers cited from your knowledge base. One txt URL is all it takes.
Bring your own Anthropic or OpenAI key and pick the model. No key? A deterministic engine still runs the flow and answers from your docs.
You define exactly what the assistant may say yes to — promo codes, annual switches, nothing more. Every offer is validated server-side.
Collect the fields you want, in the order you want. Plans, add-on upsells and copy are yours — edited live against a real preview.
Stripe's Payment Element renders inline on your own Stripe account. Card details never touch our servers.
Every question buyers ask is captured. Unanswerable ones are flagged as knowledge gaps — your checkout tells you how to improve it.
How it works
Your workspace starts from a working template — plans, copy, flow and a knowledge base you can talk to immediately.
Swap in your plans, theme and AI key. Point the knowledge base at your docs. Every edit renders against a live preview.
One click flips the draft live at your eeze subdomain — or behind your own domain. Rollback is the same click, backwards.
nimbus · draft v14 → publish
✓ catalog — 3 plans, 2 add-ons
✓ flow — 4 stages, 9 fields
✓ knowledge base — docs.nimbus.app/llms.txt (42 sections)
✓ guardrails — 2 offers allowed
✓ stripe — payment element connected
→ live at nimbus.eeze.xyz 417ms
Security & trust
Stripe's Payment Element runs on your Stripe account. Card data goes browser → Stripe. PCI DSS Level 1.
Your AI keys are sealed with AES-256-GCM and decrypted only at request time, only to call your provider.
Offers, prices and promos are validated on the server. The model can propose; it can never commit.
Checkouts run under your domain. Conversations and analytics are yours — export or delete anytime.
tls 1.3 in transit · aes-256-gcm at rest · byo provider keys · stripe pci dss level 1
“Every checkout form is a conversation where only one side is allowed to speak. Buyers arrive with questions, and we hand them input fields. eeze exists to fix that.”
— the reason eeze.xyz exists
FAQ
No. With a key (Anthropic or OpenAI) your checkout gets full conversational answers in your chosen model. Without one, a deterministic engine still runs the whole flow — plan selection, fields, payment — and answers questions straight from your knowledge base.
No. You whitelist exactly which offers exist — specific promo codes, an annual switch, nothing else. The model can only propose from that list, and every offer it proposes is re-validated server-side before it touches the order. An offer that isn't on the list simply cannot be applied.
Stripe's Payment Element renders inline in the conversation, connected to your own Stripe account. Funds settle with you directly; card details go from the buyer's browser to Stripe and never pass through eeze. Stripe is PCI DSS Level 1 certified.
A single plain-text URL — an llms.txt, a docs export, a pasted FAQ. eeze indexes it into sections and cites the exact section under every answer, so buyers can see where a claim comes from.
Yes. Every checkout is live at your eeze subdomain the moment you publish, and you can point your own domain at it whenever you're ready.
Every question is captured in your analytics. Questions the assistant couldn't answer are clustered into knowledge gaps, ranked by how often they're asked — a running to-do list for your docs, written by your buyers.
Start from a working template, make it yours against a live preview, publish to your domain. Your Stripe, your AI key, your data.