Lordbase developer documentation
Lordbase provides hosted PostgreSQL, Redis and MongoDB databases. Use the dashboard to create a database, then connect your application with the engine’s standard driver. These guides are for developers using the hosted product.
Start here: Create your first database and connect. You need a Lordbase account, an active plan with available capacity, and a local application or database client.
Choose your next step
| Goal | Guide |
|---|---|
| Get from a new account to a working query | Setup and first connection |
| Connect a Node.js application to PostgreSQL | PostgreSQL example |
| Connect Python to Redis or MongoDB | Redis · MongoDB |
| Understand credentials, IDs and workspaces | Key concepts |
| Automate database management | Management API availability and workflow |
| Look up a request or response | Complete API reference |
| Diagnose a failed request or connection | API errors · Connection failures |
Two ways your application interacts with Lordbase
The management API creates and manages resources. Your application reads and writes data through PostgreSQL, Redis or MongoDB directly. A database password is different from a developer access token; neither belongs in browser code.
Use a scoped, expiring developer token for supported management API operations. Create it in Settings, then follow the automation guide. Token permissions, workspace roles and subscription limits all apply.
Feature support by engine
| Capability | PostgreSQL | Redis | MongoDB |
|---|---|---|---|
| Provision, connect, pause/resume, delete | Available, subject to plan | Available, subject to plan | Available, subject to plan |
| Database users | Yes; permission-update caveat | ACL users and required key prefix | Database-scoped users |
| Browse data and run editor commands | SQL | Limited command set | Limited command set |
| Metrics and health | Yes | Engine-dependent metrics | Engine-dependent metrics |
| Clone | Yes, subject to plan | Not supported | Not supported |
| Backup jobs | Yes | Recovery support must be confirmed | Backup creation path exists |
| Restore through Lordbase | PostgreSQL targets only | Not implemented | Not implemented |
| Pooling, extensions, query analytics | PostgreSQL-specific; availability varies | Not applicable | Not applicable |
Read backup restrictions, database users and network enforcement before relying on these controls in production. This documentation describes the reviewed product behavior; it does not certify that every hosted dependency is currently available.