Server Configuration
Everything about configuring and managing your EdgeBase server — from access rules to rate limiting to custom email templates.
All service-key-backed server features described in this section are available across all Admin SDKs.
Configuration File
All server behavior is defined in edgebase.config.ts:
import { defineConfig } from '@edgebase/shared';
export default defineConfig({
release: false, // Set true for production (deny-by-default)
databases: {
shared: {
tables: { /* schema + access + handlers */ },
},
},
auth: { /* providers, hooks */ },
storage: { /* buckets + access + handlers */ },
rooms: { /* multiplayer rooms */ },
});
Key Topics
| Topic | Description |
|---|---|
| Config Reference | Full defineConfig() options and defaults |
| Access Rules | Declarative access control for tables and storage |
| Service Keys | Server-side auth that bypasses rules (with optional scoping) |
| Rate Limiting | 2-tier defense: software counters + Cloudflare Binding ceilings |
| Transactional email for verification, password reset, invitations | |
| Plugins | Extend EdgeBase with community or custom plugins (see dedicated section) |
| Raw SQL | Direct SQLite access via Admin SDK |
| Native Resources | Access Cloudflare KV, D1, Vectorize bindings directly |
Next Steps
| Page | Description |
|---|---|
| Config Reference | Complete configuration options |
| Access Rules | Table and storage access control |
| Service Keys | Server-side rule bypass with scoping |
| Rate Limiting | DDoS protection and abuse prevention |
| Email providers and templates | |
| Plugins | Build-time plugin system |
| Raw SQL | Direct SQL queries from Admin SDK |
| Native Resources | KV, D1, R2, Vectorize bindings |