Start with decision logging, then add observability, intelligence, and optimization workflows as your team matures.
For prototypes, local testing, and small internal decision logs.
For teams monitoring production decision systems.
For teams improving decision quality with intelligence and controlled optimization workflows.
| Capability | Developer | Observe | Optimize |
|---|---|---|---|
| Decision ingestion API | |||
| Outcome linking | |||
| Decision search & timeline | |||
| Time-series observability | |||
| Anomaly detection | |||
| Alert rules & events | |||
| Latency analytics | |||
| Evidence & actor analytics | |||
| Decision quality scoring | |||
| Outcome interpretation rules | |||
| Segments, patterns & drift | |||
| Optimization workflows | |||
| Email/password login | |||
| Workspace roles | Basic | Included | Included |
| Workspace audit logs | |||
| Retention | 7 days | 90 days | 1 year |
A single record posted to /api/v1/decisions. Outcomes are free — they don't count against your quota.
Paid plans keep ingestion available and flag the overage. A good starting model is $0.10 per 1k extra decisions on Observe and $0.06 per 1k extra decisions on Optimize.
Not yet. The current app uses email/password login, invitations, workspace roles, API keys, and audit logs. SSO and SCIM should stay off the pricing page until they are built.
A DPA can be linked from the legal footer. BAAs, formal uptime SLAs, and regulated deployment terms should be added only after your legal and operations process is ready.
Bring a sample of your decisions and we'll spin up a tenant in under a week.