Projects
Create isolated application schemas without modifying or rebuilding General PostgreSQL.
Create project
Registered projects
Loading…
Selected project
Choose a project to inspect its generic onboarding state.
Roles & API Keys
Permissions are stored as data. Role names are not hard-coded into the platform.
Select an application project from Projects first.
Create API key
Assign one or more data-driven roles:
The full key is displayed once. Save it immediately in the application's server-side secrets.
Create narrow table role
Table actions:
Roles
API keys
Frozen v3 contract
General PostgreSQL should change for platform reasons, not product feature requests.
New application
1. POST /admin/v3/projects
2. Generate a migrator key
3. POST /api/v3/projects/{project}/migrations
4. Generate runtime role/key
5. Use /api/v3/projects/{project}/tables/…
Platform boundary
General PostgreSQL knows:
project / schema / table / row
role / permission / migration
backup / audit / health
It must not know future product entities or workflows.
Migration safety
Transactional per migration
Checksummed version history
Project advisory lock
No arbitrary SQL
No DROP operations
Cross-project FK not exposed
Legacy compatibility
Existing /api/flowtrace*
Existing /api/openclaw/*
Existing /api/rss/*
Existing /api/startreck/*
Maintained for compatibility only.