Pricing
Start small, pay when the memory workload justifies it.
The pricing model is built around the resources this platform actually has to protect: API throughput, stored memory, document parsing volume, and backup coverage for paid plans.
Persistence
All plans use persistent storage.
Backups
Daily snapshots begin on Pro and Enterprise.
Metering
No token or vector-op billing in the customer layer.
Start free, upgrade when the workload earns it.
Every plan keeps data on persistent storage. Paid plans add higher throughput, daily snapshots, and softer quota behavior for teams with live customer traffic.
Free
For first production trials
Validate memory value before paying for higher throughput or scheduled backups.
Self-serve sign-up
Pro
Per workspace / month
For customer-facing workloads that need higher throughput and paid operational protection.
Manual activation while checkout is being wired
Enterprise
Enterprise
For negotiated limits, procurement review, and platform coordination.
Sales-assisted rollout
Plan comparison
What actually changes between tiers.
The step-up is not cosmetic. Pro is where higher throughput, soft quota behavior, and scheduled backups begin. Enterprise is for negotiated limits and commercial process, not just a larger free tier.
| Feature | Free | Pro | Enterprise |
|---|---|---|---|
| API calls / month | 1,000 | 50,000 | Custom |
| Stored memories | 500 | 25,000 | Custom |
| Document parses / month | 5 | 200 | Custom |
| Rate limit / minute | 20 RPM | 200 RPM | Custom |
| Limit behavior | Hard stop | Soft warning | Negotiated |
| Scheduled backups | None | Daily, 30-day retention | Daily, 30-day retention |
Paid activation
Self-serve free sign-up is live today. Paid activation is currently handled directly while checkout wiring is finalized, so Pro and Enterprise requests route through the support path instead of an instant checkout flow.
Upgrade trigger
Teams usually upgrade when they outgrow the free plan's hard stops or when paid backups become a real procurement requirement. That is the intended line between experimentation and production.
What teams ask before going live.
Billing is based on API calls, stored memories, and document parses. Neuralbase does not expose token, embedding, or vector-operation billing in the customer surface.
Dashboard access is session-based, runtime access is API-key based, and the vector layer is isolated at the per-user Qdrant collection boundary. Organization membership and key scope still control which workspace can act on data.
No scheduled backups run on the free plan. All plans use persistent storage, but daily snapshots with 30-day retention are a paid feature on Pro and Enterprise only.
Free accounts hard-stop at their plan limits. Pro accounts receive soft quota warnings and can continue past monthly allocation while the team decides whether to upgrade. Enterprise limits are negotiated.
Yes. Document parsing and memory storage are separate actions. You can parse a document, inspect the extracted output, and choose later whether to store it as memory.
The dashboard uses signed server sessions. The runtime API uses scoped API keys. Both paths flow into the same billing and quota layer so usage attaches to the correct account.
Data stays on persistent storage. VM restarts do not wipe memories or document results. Scheduled snapshots are additional protection for paid plans, not the main persistence layer.
Free sign-up is self-serve. Paid activation is currently handled directly while checkout wiring is finalized. If you need Pro or Enterprise access now, use the support link on the pricing page.