NittaqStarter
149 SAR / month
For a focused first project.
- 1 project
- 5 GB combined database size target
- 7 days backup retention
- 0.5 CPU · 1 GiB per project
- 50 direct connections per project
- Scheduled + on-demand encrypted backups
Plans and pricing.
Compare Nittaq PostgreSQL plans from SAR 149/month. Review compute, connections, database capacity, encrypted backups, retention and support.
Clear pricing.
Choose the capacity you need. Encrypted backups are included.
Save 10% yearly
Business
MORE ROOM299 SAR / month
For a growing database.
- 2 projects
- 20 GB combined database size target
- 14 days backup retention
- 1 CPU · 2 GiB per project
- 100 direct connections per project
- Scheduled + on-demand encrypted backups
Studio
599 SAR / month
For four independent ideas.
- 4 projects
- 50 GB combined database size target
- 30 days backup retention
- 2 CPU · 4 GiB per project
- 150 direct connections per project
- Scheduled + on-demand encrypted backups
Plan availability, applicable taxes and service details are confirmed before activation.
Listed resources apply to newly activated projects. Existing projects retain their activation configuration until a reviewed upgrade.
A larger workload or specific requirements? Discuss a custom plan ↗
Plan details
Core database management tools are included in every plan. Choose the project count and capacity you need, or discuss a custom configuration for heavier workloads.
On smaller screens, scroll the table sideways, or focus it and use the arrow keys.
| Resource or feature | Starter | Business | Studio |
|---|---|---|---|
| Project slots per workspace | 1 | 2 | 4 |
| Combined database size target | 5 GB · monitored target | 20 GB · monitored target | 50 GB · monitored target |
| CPU budget per project | 0.5 CPU · shared host | 1 CPU · shared host | 2 CPU · shared host |
| Memory limit per project | 1 GiB | 2 GiB | 4 GiB |
| Direct connections per project | 50 concurrent customer connections | 100 concurrent customer connections | 150 concurrent customer connections |
| Database engine | PostgreSQL · standard SQL connection | PostgreSQL · standard SQL connection | PostgreSQL · standard SQL connection |
| Isolation | Separate database, credentials and container per project | Separate database, credentials and container per project | Separate database, credentials and container per project |
| Scheduled backups | Daily target for running projects; service availability applies | Daily target for running projects; service availability applies | Daily target for running projects; service availability applies |
| Backup retention | 7 days · recorded expiry per backup | 14 days · recorded expiry per backup | 30 days · recorded expiry per backup |
| On-demand backups | Included · one operation at a time per project | Included · one operation at a time per project | Included · one operation at a time per project |
| Backup protection | AES-256-GCM encryption and integrity verification | AES-256-GCM encryption and integrity verification | AES-256-GCM encryption and integrity verification |
| Restore workflow | New project · requires a free project slot | New project · requires a free project slot | New project · requires a free project slot |
| Point-in-time / off-site recovery | Not included in standard plans | Not included in standard plans | Not included in standard plans |
| Reads, writes and application users | No separate count-based plan quota; compute and connection limits apply | No separate count-based plan quota; compute and connection limits apply | No separate count-based plan quota; compute and connection limits apply |
| Network transfer and disk performance | Deployment-specific; confirmed before activation | Deployment-specific; confirmed before activation | Deployment-specific; confirmed before activation |
| Project controls | Start, stop, delete and credential rotation | Start, stop, delete and credential rotation | Start, stop, delete and credential rotation |
| Support | Support tickets and email follow-up | Support tickets and email follow-up | Support tickets and email follow-up |
| Hosting region and service commitments | Agreed before activation; no published uptime or response-time SLA | Agreed before activation; no published uptime or response-time SLA | Agreed before activation; no published uptime or response-time SLA |
| AI and backend services | Model inference, managed vector search, app auth, object storage and functions are not included | Model inference, managed vector search, app auth, object storage and functions are not included | Model inference, managed vector search, app auth, object storage and functions are not included |
Choosing a plan for your workload
Do connection limits count application users?
No. These are simultaneous PostgreSQL sessions, including idle connections held by your application pool. Reusing connections lets many application users share a smaller pool. Connection capacity does not guarantee that every session can run a heavy query at full speed at the same time.
Is there a fixed SQL query time limit?
New projects have no blanket statement timeout; your application can set an appropriate timeout for its own workload. An open transaction left idle for 60 seconds is closed to prevent abandoned transactions from holding locks. This safeguard does not limit the duration of an actively running query. Existing projects retain their recorded defaults until a reviewed upgrade.
Is database storage pooled across projects?
Yes. The 5, 20 and 50 GB targets apply to the combined measured database size in your workspace, including tables and indexes. They are monitored targets, not reserved disks or hard disk quotas. Backup archives are separate from this database size measurement.
Does a larger plan give each project more compute?
Yes. Every upgrade increases CPU, memory and direct connections per project, alongside project slots and combined database capacity. The listed resources apply to newly activated projects. Existing projects retain their activation configuration until a reviewed upgrade. If you need resources beyond Studio, request a custom configuration.
What happens when I reach a limit?
New projects are blocked when all workspace slots are occupied or the host cannot accommodate their resources. PostgreSQL rejects connections above the configured customer connection limit. CPU and memory limits protect each project and the shared host. Approaching the database size target shows a workspace warning; it is not an automatic storage cutoff. There is no separate plan quota for SQL reads, writes or application users. Discuss growth with us before reaching capacity; price changes are agreed before activation.
Can I use Nittaq for an AI application?
Use PostgreSQL for application records, conversation metadata and structured data, and connect your own model provider from your backend. Standard plans do not include GPU compute, model inference credits, managed embeddings or a managed vector search service. Extension availability and AI workload capacity need review before activation.
Are backups the same as high availability?
Backups preserve recoverable snapshots; they do not provide automatic failover or point-in-time recovery. A restore creates a separate project from a ready, unexpired backup and needs an available project slot. Scheduled backups target a daily cadence while the project is running; review the completed backup timestamp and expiry in your dashboard.