Free
For personal projects and small groups of up to 5 users.
$0per month
- 200 credits each month
- Up to 5 users, people and agents alike
- Up to 1 compute unit
- Up to 500 MB of data storage
- Support: documentation only
Run Semantius in the cloud and pay in credits for what your database uses, not per user. Or run it yourself, free and open source.
Yearly plans are paid upfront for 12 months. Credits are still granted each month.
For personal projects and small groups of up to 5 users.
$0per month
For teams of any size, with no limit on users.
$24per month
$20per month, billed yearly
$240 paid upfront for 12 months
For larger workloads, with up to 32 compute units and no storage limit.
$45per month
$37per month, billed yearly
$444 paid upfront for 12 months
Spending is limited to the credits you hold. Top-ups are manual, so there are no unexpected charges.
| Feature | Free | Starter | Pro |
|---|---|---|---|
| Price, monthly | $0 per month | $24 per month | $45 per month |
| Price, yearly (paid upfront for 12 months) | Not applicable | $20 per month ($240 upfront) | $37 per month ($444 upfront) |
| Credits included (granted each month) | 200 | 250 | 500 |
| Users (people and agents each count as one) | 5 | No limit | No limit |
| Maximum compute | 1 compute unit | 4 compute units | 32 compute units |
| Data storage limit | 500 MB | 1 GB | Unlimited, paid in credits |
| Top-ups | No | Yes | Yes |
| Support | Documentation only | Support | Support |
| Webhook receivers (let other systems send records in through a signed webhook) | No | No | Yes |
Every cloud plan includes credits each month, and everything your platform uses is paid for in credits. A compute unit is a fraction of a virtual CPU plus 1 GB of memory, and one credit buys one compute unit for 15 minutes.
The database pauses when it is idle, and compute is only counted while it runs. So compute depends on how long the database is active, not on how many people use it. It pauses after a short idle period and wakes again when it is next used.
What each thing your platform uses costs, in credits.
| What | Unit | Credits |
|---|---|---|
| Compute | 1 compute unit for 1 hour | 4 |
| Data storage | 1 GB for a month | 20 |
| Egress (data transfer out) | 1 GB | 12 |
| Emails sent | 1,000 emails | 20 |
Top-ups add credits when your monthly credits are not enough. They are available on Starter and Pro; the Free plan cannot be topped up.
| Pack | Price |
|---|---|
| 100 credits | $13.50 |
| 200 credits | $22 |
| 1,250 credits | $119 |
Compute depends on how long the database is active, not on the number of users. These three setups are illustrative: the usage is assumed, and the credits are worked out from the rates above. Each one shows the plan that costs least for it.
A snag list or a rental tracker, shared with a helper.
| Item | Assumed usage | Credits |
|---|---|---|
| Compute | 1 compute unit, 30 hours a month (about 1 hour of activity a day) | 120 |
| Data storage | 0.3 GB | 6 |
| Egress | 0.5 GB | 6 |
| Emails | 300 emails | 6 |
| Total | credits a month | 138 |
Free: $0 a month.
6 people and 2 agents, working office hours.
| Item | Assumed usage | Credits |
|---|---|---|
| Compute | 1 compute unit, 176 hours a month (office hours) | 704 |
| Data storage | 1 GB | 20 |
| Egress | 3 GB | 36 |
| Emails | 1,500 emails | 30 |
| Total | credits a month | 790 |
Pro: $45 with 500 credits, plus top-ups for about 290 credits: about $73 to $81 a month, depending on pack size.
About 50 people with agents, around the clock.
| Item | Assumed usage | Credits |
|---|---|---|
| Compute | 2 compute units, 730 hours a month (around the clock) | 5,840 |
| Data storage | 10 GB | 200 |
| Egress | 40 GB | 480 |
| Emails | 20,000 emails | 400 |
| Total | credits a month | 6,920 |
Pro: $45 with 500 credits, plus top-ups for about 6,400 credits: about $650 a month.
Choosing between Starter and Pro: above about 450 credits a month, Pro costs less than Starter with top-ups.
Would you rather not run it yourself? See the Cloud plans.
MIT license
Everything you need to run Semantius on your own server is free and open source under the MIT license. Support is sold separately.
All of it is released under the MIT license, and all of it is free to run.
The software is free, and support is sold separately. Paid plans have no incident counting: raise as many issues as you need, with no cap on the hours spent on one.
Free
$1,800per year
$6,000per year
By negotiation
Prices are in US dollars, billed annually in advance. P1 is the most urgent kind of request; the response targets are below. To buy a plan or a service, email hello@semantius.com.
Support works during business hours, 09:00 to 17:00 US Eastern, Monday to Friday, except published closure dates. A request that arrives outside those hours counts from the start of the next business hour.
| Severity | What it means | Standard | Priority |
|---|---|---|---|
| P1 | Production down, or data at risk | 2 business days | 1 business day |
| P2 | Major function impaired, no workaround | 3 business days | 2 business days |
| P3 | Minor issue, workaround available | 5 business days | 5 business days |
| P4 | Question, guidance, configuration | 5 business days | 5 business days |
These are response targets, not resolution times, and there is no uptime SLA. Semantius does not operate your infrastructure. The commitment is that a person who wrote the code reads your problem within the stated time; how long a fix takes depends on your environment.
There is no out-of-hours or 24/7 cover on any plan.
Support covers the Semantius code and the published deployment. Getting your own system designed, modeled and live is a service: a Deployment Review, or hourly work.
| Activity | Support | Services |
|---|---|---|
| Diagnosing defects in the unmodified pg_semantius extension, the app, or the published self-hosted stack | Yes | No |
| Security advisories and hotfixes | Yes | No |
| Startup, configuration and upgrade troubleshooting for the published Docker Compose stack | Yes | No |
| Environment variable, identity provider and JWKS configuration for the published stack | Yes | No |
| Migration and upgrade guidance along the published pg_semantius migrate path | Yes | No |
| Explaining how the catalog, rule engine and audit trail behave | Yes | No |
| Designing or debugging your own model: entities, fields, rules, JsonLogic, workflows | No | Yes |
| Your application code, custom clients or your own MCP servers | No | Yes |
| Your operating system, VM, cloud account, network, firewall, TLS certificates or backups | No | Yes |
| Postgres tuning beyond the extension's own queries | No | Yes |
| Configuration inside your identity provider | No | Yes |
| Any deployment modified from the published distribution | No | Best effort |
| Recovering data lost through changes made outside the product | No | Best effort |
| On-site work | No | Not offered |
Two deployment sessions, and hourly work for anything outside the support scope.
$750 up to 3 hours
One working session over your deployment: your Compose or Kubernetes configuration, your reverse proxy and TLS, and your identity provider and JWKS wiring. You hear what should change, and get a short written summary rather than a report. There is no preparation pass, Postgres sizing or backup design. Findings may be used anonymously to improve the product and its documentation.
$2,500 up to 10 hours
A preparation pass over your configuration, a working session with your team, and a written report. It covers your Compose or Kubernetes configuration, reverse proxy and TLS, identity provider and JWKS wiring, backup and restore plan, and Postgres sizing for your number of users.
$250 an hour
For work outside the support scope, sold in prepaid blocks of 5 hours.
Everything you need to know about the product and billing.