What we are building and what is next
This is the real roadmap — shipped items are labeled shipped, work in progress is labeled in-progress, and nothing is marked done until it is. Quarter targets are estimates, not guarantees.
Planned
Committed to building. Quarter targets are estimates, not guarantees.
Edge functions in the console import wizard
The CLI already moves an imported project's edge functions from your local checkout (scribase import --functions-dir). The console import wizard will get the same step: upload a functions directory or archive and deploy it through the normal function deploy.
Metrics dashboard
Built-in Postgres and application metrics — connections, query latency, storage IOPS — surfaced in the console without requiring an external Grafana stack.
Query insights
Slow-query capture and index recommendations driven by pg_stat_statements, surfaced directly in the console so slow queries are visible without a separate monitoring tool.
Multi-region read replicas
Attach read replicas in additional regions to reduce latency for globally distributed applications without duplicating the full write path.
Shipped
Available in production today.
Control API (OpenAPI)
Full OpenAPI surface for every management action — projects, migrations, functions, secrets, backups, and billing. Every mutation carries an idempotency key and an operation ID for safe agent and CI use.
Verified restore with evidence
Recovery proves itself. Each restore ships row-count parity, SHA-256 checksums, policy parity, and a real login proof — artifacts you can inspect and show auditors rather than a green checkmark you have to trust.
Preview branches
Instant copy-on-write preview environments scoped to a pull request. Branches are stripped of production secrets on creation and swept on a TTL when the PR closes, so stale branches never become credential leaks.
Import and export bundles
scribase import moves schema, data, auth users, storage objects, and RLS policies with IDs preserved — no forced password resets. scribase export produces a portable bundle that boots elsewhere.
Agent-native scribase CLI
One binary for local and hosted work: scribase dev boots Postgres, auth, storage, realtime, and functions locally; branch, migrate --dir, import, export, queue, and schema commands drive the /v1 API, and every mutation returns an operation ID.
RLS policy cost linter
Warns when a row-level security policy will cause a full-table scan so teams keep isolation switched on without paying for it in query latency.
Edge-function deploys over the API
Deploy, list, and invoke an environment's edge functions through the authenticated /v1 API and the scribase TypeScript SDK (functions.deploy, functions.list, functions.invoke), on the open-source Deno edge-runtime and the standard /functions/v1 path.
MCP server
scribase-mcp exposes the control surface to AI agents over the Model Context Protocol: reads run immediately, every write waits for an explicit confirm, and schema changes must pass an RLS isolation test first. Setup lives at /mcp and in the console under MCP server.
SSO (SAML 2.0 / OIDC)
Console single sign-on through your own identity provider over OIDC or SAML 2.0. Verify your email domains with a DNS record, let people on them join automatically with a role you choose, test the connection, then require SSO for everyone but owners. Configure it in the console under Single sign-on.
Team audit logs
Append-only organization audit log of every mutating API call — actor, action, resource, and time. Filterable in the console under Audit logs and paginated over GET /v1/organizations/{org}/audit-events for SIEM ingestion or DPA evidence.
Familiar CLI command parity
Matching verbs for the backend CLI workflows teams script today, so existing Makefiles and CI pipelines move over with a URL-and-keys swap: scribase functions deploy, scribase secrets set, scribase migrate --dir, scribase db pull, scribase gen types, and scribase login all ship today.
BYOC Helm chart
Run Scribase inside your own Kubernetes cluster with the Helm chart in deploy/helm/scribase: the control plane always, plus an optional shared data plane. Same verified restore and preview capabilities as managed Scribase, with least-privilege operator roles and no cluster-admin in workloads.
Password reset for built-in sign-in
Self-hosted control planes using the built-in admin login can reset a forgotten password: the administrator creates a single-use reset link for a member, and when a mail relay is configured members can request an emailed link from the sign-in page.
Considering
On the list but not yet scheduled. Community signal shapes priority.
Terraform provider
Official Terraform provider for managing Scribase projects, secrets, custom domains, and team members declaratively alongside other infrastructure.
GitHub Actions integration
First-class GitHub Actions for migration preview, deploy, and smoke-test so CI pipelines stay consistent with local scribase CLI flows without custom shell scripts.
Have something to add?
Tell us the problem you are trying to solve and what it would unblock — that context moves items faster than feature requests alone.
Roadmap questions
How do quarter estimates work?
Quarter targets on planned and in-progress items are estimates based on current priorities — not hard commitments. If a quarter slips we update the label rather than keeping a stale one. Items in the "Considering" column have no quarter target yet.
How can I influence the roadmap?
Send a feature request through the contact form or email support@scribase.com with your use case. Real-world problem descriptions have moved items from "Considering" to "Planned" before.
Is SSO available?
Yes. Console single sign-on works with any OIDC provider or SAML 2.0 identity provider. An owner or admin connects the provider, verifies the company email domain with a DNS TXT record, runs a connection test, and can then require SSO for everyone except owners.
Can I run Scribase in my own cluster (BYOC)?
Yes. The Helm chart in deploy/helm/scribase installs the control plane in your own Kubernetes cluster, with an optional shared data plane, and includes the same verified restore, preview branches, and CLI as managed Scribase. For one server instead of a cluster, the Docker Compose single-box layout runs many small projects on one VPS.
What does "Considering" mean?
Considering means the item is on our list and we are gathering signal before committing to a quarter. It is not in active development, but it is not dismissed either. Community feedback shapes what moves to Planned.