The dashboard
Nobody looks after the meeting
Built on definitions nobody agreed to, so every team defends a different number — and nobody trusts any of them.
When something in your business stops holding, you'll know.
Soltura watches what your business has committed to: purchases that complete, invoices that get paid. When something fails, it gets a name and an owner, and it isn't resolved until the number is back where it belongs.
Are checkouts completing as we agreed?
No. Checkout completion is at 40% against the agreed ≥ 80%, since August 8. Commerce owns this promise. Here is the history: four earlier episodes and one still open.
Synthetic demo data
Checkout completion
40% against ≥ 80% agreed. Outside the agreed range since August 8: INC-1104 is still open. The four earlier episodes recovered.
Open this history in the live demo: demo.soltura.ai/c/checkout_completion/history
Where are we losing them today?
Today, 100 of 250 qualified sessions confirmed an order: 40%. The largest loss is at payment: 168 started paying and 108 were authorized, so 60 never got past that step.
Synthetic demo data
Checkout completion
Today. The same 250 eligible checkout attempts, from qualified session to confirmed order.
Open today's view in the live demo: demo.soltura.ai/c/checkout_completion/now
Is anyone on this?
Not yet. INC-1104 opened on August 8 and nobody has picked it up. The last time this slipped, in June, Alex Rivera from Commerce took it:
- Opened. Outside the agreed ≥ 80%.
- Alex Rivera picked it up.
- Note: “Payment-step retries. Cause of the retry is not established.”
- Recovered. Back inside ≥ 80%.
This is how it reads in Claude or ChatGPT with your account connected. The data here is a demo.
Installs from Claude Code, Codex, or Cursor. The first session agrees the question with you. It does not open a pull request. After you confirm, you can see that question in Cloud, waiting for events.
The problem
Conversion dropped on Friday.You found out on Monday.And nobody knew if it was the checkout or the tracking.
Business numbers get answered once and nobody looks again. When they fall, a chart can't tell lost sales from events that stopped arriving. And the alert, if there is one, has no owner.
And when someone does look, every team is measuring something different: overdue since the due date, the reminder, or the promise to pay? Soltura pins the definition down before anything is measured.
What Soltura does
One promise, one range, one owner.
Agree what has to hold.
“Priority products don't run out before restock arrives.” An explicit definition and boundary, reviewed like code.
Soltura keeps measuring it.
If everything is inside its range, there is nothing to look at. A quiet morning is good news.
If it fails, it shows up with a name and an owner.
Someone picks it up and investigates from what Cloud already knows, with their agent and their tools. What they find gets noted.
It closes when the number comes back.
Nobody closes an incident by writing “fixed”. The data does.
What you already have
You already knew what to watch.What you didn’t have was someone watching it.
The alert
Fires and nobody picks it up
A threshold in the monitoring tool or a Slack channel: no owner, no close, and no way to tell whether the business failed or the measurement did.
Soltura
Owned, agreed, closed by the data
The promise is defined and reviewed like code. When it fails, someone has it. It closes only when the number returns.
Questions already answered
The answer is waiting for you.
Bring your own question, or start from one of these. Every answer below is captured from the running product using synthetic demo data.
ConversionHow many checkouts are completed?
Checkout completion is outside its range. Soltura flags it; you decide how to dig in — from Cloud or by continuing in the skill. Once it recovers, the incident is logged and its history stays available for future incidents.
See what happens after it slipsLive answer
Know where to act. Know whether it holds.
Overview points at what needs attention. Each promise brings its trend, its evidence, and the next decision. If a promise stops holding, the people who need to move hear about it — and hear again when it holds.
Next decision · Inventory operationsExpedite or rebalance the short-cover products.
Needs attentionNeeds attention
Can we keep priority products available?
Observed outcome2 de 4Products run out first
Reviewed boundary2 daysCover buffer
Products without dependable stock evidence are left out, not estimated.
Next decision · Inventory operationsExpedite or rebalance.
How it’s possible
Your coding agent agrees the question. Instrumentation comes later.
Soltura doesn’t ask for an event plan. You ask the agent that already knows your code — Claude Code, Codex, or Cursor — and it first agrees what counts. When you are ready to measure it, that later session proposes the minimum instrumentation as a normal pull request. Only approved events leave the repository; the code never does.
- In your repositoryTyped instrumentation, tests, and one signal contract.
- In reviewA normal pull request, diffable line by line.
- After mergeAggregate events only. No payloads, no source, no secrets.
Your code stays local.
Source code, agent conversations, diffs, logs, raw payloads, and secrets stay in your environment. Soltura receives only the signal contract and aggregate events your team approves.
See an example change proposed by the skill
agent›
Use the Soltura skill. Can customers complete purchases reliably?
soltura›
I mapped one outcome and the events needed to measure it.
- outcome
- Checkout completionconfirmed success: order_confirmed
- owner
- Commerceaccountable for the next decision
plan›
minimum evidence path
- 01
checkout_started - 02
checkout_payment_submitted - 03
payment_resolved - 04
order_confirmed
review›
Approve the contract, files, and tests? [y/N] y
apply›
reviewed change prepared
- soltura.yaml
- typed instrumentation + tests
pull request ready for reviewafter merge: approved signals → Cloud
cloud›
- outcome
- Purchase completion
- owner
- Commerce
- status
- needs attention
- result
- 33.8% · measurement limited
What it costs
Priced by the question, not by the seat.
Start free on one real question. When it outgrows the free band, a simple recurring agreement adds capacity — what gets metered is the commitment you keep answerable, never the people reading the answer.
Free
Free- Active commitments
- 1
- Included events / month
- 250,000, hard-capped
- Excess events
- Pause, no invoice
- Raw events retained
- 30 days
Team
€99/month- Active commitments
- 5
- Included events / month
- 1.5M
- Excess events
- €0.10 per 1,000, capped
- Raw events retained
- 90 days
Business
Recommended€349/month- Active commitments
- 20
- Included events / month
- 6M
- Excess events
- €0.10 per 1,000, capped
- Raw events retained
- 180 days
Enterprise
Let’s talk- Active commitments
- Contracted
- Included events / month
- Committed volume
- Excess events
- Agreed terms
- Raw events retained
- Tailored
Compare every plan detail
Price
- Free
- Free
- Team
- €99/month
- Business
- €349/month
- Enterprise
- Let’s talk
Active commitments
- Free
- 1
- Team
- 5
- Business
- 20
- Enterprise
- Contracted
Included events / month
- Free
- 250,000, hard-capped
- Team
- 1.5M
- Business
- 6M
- Enterprise
- Committed volume
Excess events
- Free
- Pause, no invoice
- Team
- €0.10 per 1,000, capped
- Business
- €0.10 per 1,000, capped
- Enterprise
- Agreed terms
Raw events retained
- Free
- 30 days
- Team
- 90 days
- Business
- 180 days
- Enterprise
- Tailored
Question history
- Free
- Complete
- Team
- Complete
- Business
- Complete
- Enterprise
- Complete
Workspaces
- Free
- 1
- Team
- 3
- Business
- 10
- Enterprise
- As many as you need
Collaborators
- Free
- Included
- Team
- Included
- Business
- Included
- Enterprise
- With governance
Context collection
- Free
- None
- Team
- 1,000 attempts, then pause
- Business
- Contracted
- Enterprise
- Contracted
Support
- Free
- Community
- Team
- Standard
- Business
- Priority
- Enterprise
- Contracted SLA
SSO and advanced governance
- Free
- —
- Team
- —
- Business
- —
- Enterprise
- Included in the conversation
| Feature | Free | Team | Business | Enterprise |
|---|---|---|---|---|
| Price | Free | €99/month | €349/month | Let’s talk |
| Active commitments | 1 | 5 | 20 | Contracted |
| Included events / month | 250,000, hard-capped | 1.5M | 6M | Committed volume |
| Excess events | Pause, no invoice | €0.10 per 1,000, capped | €0.10 per 1,000, capped | Agreed terms |
| Raw events retained | 30 days | 90 days | 180 days | Tailored |
| Question history | Complete | Complete | Complete | Complete |
| Workspaces | 1 | 3 | 10 | As many as you need |
| Collaborators | Included | Included | Included | With governance |
| Context collection | None | 1,000 attempts, then pause | Contracted | Contracted |
| Support | Community | Standard | Priority | Contracted SLA |
| SSO and advanced governance | — | — | — | Included in the conversation |
| Get started | Start free | Start with Team | Start with Business | Talk to us |
Invalid, rejected, and duplicate events never count. You pay for accepted evidence — nothing else.
Which promise can’t break without you knowing?
250,000 free events a month. No card. Your code never leaves the repository