NittaqA clear path from backup to recovery.
A backup is useful when you know what it contains, when it completed and how to restore it. Nittaq combines encrypted PostgreSQL backup archives, recorded expiry dates and a restore workflow that creates a separate database project.
Scheduled and on-demand backups in every plan
Running projects target a daily backup cadence, subject to service availability and completion of queued operations. You can also request a backup manually before a migration or important data change. Review the last completed backup timestamp in the dashboard; a schedule alone is not evidence that a usable backup exists.
Encrypted archives with integrity checks
Backup archives use AES-256-GCM authenticated encryption. The restore workflow verifies archive integrity before loading data. Encryption protects the archive; it does not turn a same-host backup into an off-site disaster recovery copy. Standard plans do not include off-site replication.
Know your retention window
Newly activated Starter, Business and Studio projects retain backups for 7, 14 and 30 days respectively. Existing projects retain their recorded backup retention until a reviewed upgrade. Each backup shows its own expiry date, and only ready, unexpired backups can be restored. Deleting a project can preserve its existing backups until expiry, unless you explicitly choose to purge them. Backup archive size is separate from the measured database size target.
Restore to a new project
Select a ready backup and restore it into a new project. The workflow requires an available project slot and sufficient capacity. A Starter workspace with its single slot already occupied needs a capacity plan before restoring alongside the existing project. Check the restored data and application connection before switching your application to the new project.
Plan recovery around your actual risk
Snapshot backups are not point-in-time recovery, automatic failover or a guaranteed recovery time. The standard plans publish no RPO or RTO commitment. If your application requires regional disaster recovery, a specific maximum data-loss window or an uptime SLA, discuss those requirements as part of a custom plan before activation. Rehearse restores and maintain independent exports where your business requires them.