BaaS Introduction

Backup as a Service (BaaS) helps teams set up reliable backup and restore workflows quickly, without having to build and maintain their own backup systems.

It offers robust SDKs to help you implement authentication, workspace-level access control, automated backup jobs, snapshot-based recovery, and backup lifecycle operations—without having to work directly with raw APIs. All backup data is securely stored on Lighthouse for reliable, long-term retention.

What you can do with BaaS

• Authenticate using email/password or SIWE
• Organize backups by workspace for teams and projects
• Manage members, roles, and scope-based permissions
• Create and rotate API keys for cron/CI backup jobs
• Encrypt backup data to protect sensitive information in transit and at rest
• Compress backup data to reduce storage size and speed up transfer
• Verify backup integrity with checksums before recovery and restore operations
• Upload backup data and manage snapshots

How this documentation is organized

The BaaS docs are centered around a practical backup workflow:

1. Database Backup Guides
2. Authentication
3. Workspaces and members
4. Roles, scopes, and permissions
5. API Keys
6. Backup database
7. Upload Backup Data and Manage Snapshots

Developer workflow

For most teams, the implementation pattern is:

• Run a scheduled database dump job that updates one dump file daily
• Call the SDK Backup() flow from automation
• Use snapshots as immutable restore points
• Periodically validate restore paths in a recovery drill

BaaS is built to be reliable, secure, and straightforward to operate from day one.