PostgreSQL
Native archive inspection, restore validation, schedules, retention, and original or alternate target restores.
Senal Recover
Database backup and restore you can prove.
Protect PostgreSQL, MySQL, and Firebase Firestore with scheduled backups, encrypted credentials, engine-aware validation, restore testing, and owner-controlled recovery in the same platform that monitors your services.
Database protection
Production workspaceData sourceEngineLast backupValidation
Primary applicationPostgreSQL8 minutes agoRestore tested
Commerce recordsMySQL21 minutes agoValidated
Customer workspaceFirestore43 minutes agoExport verified
Supported databases
One recovery workflow across three database engines
Engine-specific tooling underneath, one operational and audit model for your team.
MySQL
mysqldump-compatible backup artifacts with validation and restore workflows equivalent to PostgreSQL.
Firebase Firestore
Managed Firestore exports and imports through a configured Google Cloud Storage bucket or URI prefix.
Recovery controls
Backups are only useful when they restore
Senal Recover treats validation, credential ownership, and restore authorization as part of the backup system.
Automated backup policies
Schedule backups with tenant-specific retention, storage, and plan controls.
Engine-aware validation
Inspect PostgreSQL archives, MySQL dumps, and Firestore export manifests before restore.
Restore testing
Prove recoverability against organization-owned scratch targets before an incident.
Credential lifecycle
Encrypt, label, rotate, validate, associate, and safely delete database credentials.
Explainable drift detection
Flag abnormal backup size and duration using transparent historical comparisons.
Controlled restore execution
Recommend validated restore points and restrict destructive restores to organization owners.
Operational workflow
From connection to controlled recovery
Connect
Save an encrypted PostgreSQL, MySQL, or Firebase credential and validate access.
Protect
Run an immediate backup or define a schedule, retention window, and storage destination.
Prove
Inspect every artifact and optionally restore it into your tenant-owned scratch environment.
Recover
Select a validated restore point and restore to the original or an approved alternate target.
Tenant security
Credentials stay scoped to the organization that owns them
Database secrets, Firebase service accounts, scratch validation targets, and storage credentials are encrypted, tenant scoped, and resolved only when an authorized worker job needs them.
- Credential lifecycleRename, rotate, revalidate, associate, and safely delete credentials.
- Restore authorizationOnly organization owners can execute destructive restore operations.
- Audit evidenceConnection, credential, backup, validation, and restore events remain attributable.
- Tenant scratch targetsEach organization supplies its own isolated restore-validation environment.
FAQ
Database backup and restore questions
What is Senal Recover?
Senal Recover is a database backup and restore product built into Senal Ops. It protects a database with scheduled or manual backups, validates every backup, flags drift when a backup looks abnormal, and restores a validated backup on demand.
Do I need a separate account for Senal Recover?
No. Senal Recover uses the same login, organization, and billing plan as Senal Ops monitoring. There is no separate signup or subscription.
Which databases can Senal Recover protect?
Senal Recover supports PostgreSQL, MySQL, and Firebase Firestore. PostgreSQL and MySQL use native dump and restore tooling. Firestore uses managed exports and imports through Google Cloud Storage.
How does backup validation work?
Every successful backup receives engine-specific validation. PostgreSQL archives, MySQL dumps, and Firestore export manifests are inspected before they become restore candidates. Business plans can add tier two validation by restoring or importing into a tenant-configured scratch target.
How does Senal Recover pick a restore point?
It recommends the most recent restore-validated backup with no unresolved alerts, and explains that recommendation in plain language rather than a black box score. Failed or unvalidated backups are blocked from restore unless restore validation is explicitly disabled for development.
Who can execute a restore?
Only the organization owner, since a restore writes into the target data source. A restore also requires a recently issued session, so you may be asked to sign in again before restoring.
Where are backups stored?
By default, backups are stored in a shared Senal platform bucket built on NEXUS AI object storage. Organizations that need dedicated storage or custom retention can add their own S3 compatible storage destination.
Which plans include Senal Recover?
Senal Recover is available on Pro and Business. Pro supports backup and restore for up to two protected databases with automated schedules. Business supports up to five protected databases and adds tier two restore testing with longer retention.
Are backup connection strings encrypted?
Yes. Database connection strings and Firebase service-account configurations are encrypted at rest with a dedicated Recover encryption key. Saved credentials can be renamed, rotated, validated, associated with protected databases, and deleted when no connection or restore target depends on them.
What does Firebase Firestore require?
The Firebase configuration must include a service account plus either outputUriPrefix or storageBucket. Exports are written to Google Cloud Storage, so the service account needs the required Firestore export and bucket permissions.
How is tenant-specific restore validation configured?
Each organization manages its own encrypted scratch credentials in the Senal Recover interface. The worker resolves the organization credential at validation time, so one tenant never relies on another tenant's scratch database or Firebase project.
Protect the data behind your services.
Start with a manual validated backup, then add schedules and restore testing.