BACKEND
Backend and Database Builder
The Backend and Database Builder lets you design, generate, and manage backend systems without writing boilerplate code. It includes database modeling, schema building, auto-generated CRUD APIs, relational functionality, migrations, an API explorer, and environment management.
Overview
- Database schema design and configuration
- Visual schema modeling
- Auto-generated CRUD APIs
- Database migrations
- Environment management
- Built-in API Explorer
- Role-based access control and user management
- Environment-specific configuration
Supported database engines
- SQLite (with and without WAL)
- MySQL, MariaDB, and TiDB
- PostgreSQL
- CockroachDB
- PlanetScale
- Cloudflare D1
- Vercel Postgres
- AWS Aurora (PostgreSQL / MySQL)
Creating a Database
Create managed databases directly from your project. PostgreSQL is recommended for production apps; MySQL, MariaDB, Cloudflare D1, and Vercel Postgres are also supported.
- Open your project and go to the Database section in project management.
- Click Create Database.
- Choose the engine, region, and additional settings.
- Confirm creation and wait for the database to become ready.
- Copy the connection string and use it in your app or export configuration.
Schema Builder
The Schema Builder provides a visual interface for modeling tables, fields, and relations without hand-writing SQL for every change.
- Drag-and-drop interface for modeling tables and fields
- Field definitions with type validation
- Relation management between models
- Auto-generated migration files
- Environment-specific schema configurations
- Preview changes before applying to production
Supported field types
- String, Number, Boolean, Date, Timestamp, JSON
- Foreign keys and relational links
- File — with cloud storage integration for uploads and assets
Example schema
const schema = {
name: string(),
email: string().unique(),
age: number().optional(),
};Auto CRUD API Generation
For each table in your schema, Electroplix automatically generates REST-style endpoints you can call from the Dynamic Engine, AI Builder output, or exported code.
- GET (list) — Fetch paginated records
- POST (create) — Create a new record
- GET (single) — Fetch one record by ID
- PUT (update) — Update an existing record
- DELETE — Remove a record
Supported runtimes
- Express.js, Fastify, and Hono
- Cloudflare Workers
- AWS Lambda
An auto-generated frontend SDK is available so UI components can consume your APIs with typed helpers instead of raw fetch calls.
Relations and Migrations
Relations
- One-to-One — Single related record per entity
- One-to-Many — Parent with multiple child records
- Many-to-Many — Junction tables for complex associations
Migrations
- Automatic generation of SQL migration files from schema changes
- Version control for database changes aligned with your project history
- Rollbacks when you need to undo a migration
- Environment-specific migrations for dev, staging, and production
Roles and Access Policies
Define granular control over who can read, create, update, or delete data. Policies can be based on user roles, record ownership, or custom logic.
Example policy
allow('read').on('posts').where('is_published', true);Combine role-based rules with authentication providers (email, OAuth, sessions) to secure admin panels and public-facing APIs.
Environment Management
Manage multiple environments — development, staging, and production — each with its own database connection, variables, and configuration.
- Separate connection strings and secrets per environment
- Environment-specific schema and migration targets
- Promote changes from dev to staging to production with review
API Explorer
The built-in API Explorer lets you test and inspect generated endpoints without leaving the Electroplix workspace.
- Auto-generated API documentation from your schema
- Request builder for trying GET, POST, PUT, and DELETE calls
- Response viewer with status codes and JSON payloads
Testing
Validate backend behavior before shipping with unit and integration testing support, plus tools for mocking and seeding data.
- Seed sample data for local development and demos
- Mock API responses while frontend work is in progress
- Run integration tests against staging environments
Storage and File Uploads
File fields in your schema connect to cloud storage for uploads, avatars, documents, and other assets. Configure buckets and access rules per environment.
- Upload from forms and backend-connected UI components
- Store file metadata alongside relational records
- Restrict access with the same roles and policies as your API layer