Private beta open

Write queries. Ship changes.
One platform.

Connect, query, and ship database changes across every major database, without juggling separate tools. Built for teams that take production seriously.

Request beta access Book a walkthrough
simcha, change plan 
$ simcha change plan migrations/2026_user_email_lower.sql

→ analyzing planned statements...
  ✓ connect: postgres-prod-east [v15.4]
  ✓ dry-run on shadow DB: 12ms
  ✓ reversible: rollback script generated
  ! data dependency: 8.4M rows touched
  ✓ blocking lock check: no long-running tx

→ proposed change:
ALTER TABLE users ADD COLUMN email_lower TEXT
  GENERATED ALWAYS AS (lower(email)) STORED;
CREATE UNIQUE INDEX CONCURRENTLY users_email_lower_idx
  ON users (email_lower);

→ awaiting approvals: required
  pending: @platform-lead, @data-lead

your relational database. your nosql. your graph. your column store.

Every dialect your team runs. One workspace.

See the full compatibility matrix for adapter status and dialect-specific notes.

Your database tooling is fragmented. It shouldn’t be.

Most teams stitch together a query IDE, a schema-diff tool, a migration runner, an approvals tracker, and a deployment dashboard. Different tools, different auth surfaces, different places where things go wrong.

-Today
  • Different IDEs for PostgreSQL, MySQL, Mongo
  • Schema changes live in chat threads
  • Migrations applied by hand on prod
  • “Who approved this?” nobody knows
  • Rollback plan: pray
+With DB Studio
  • One IDE across every dialect your team runs
  • Changes tracked as versioned scripts
  • Promotions go through approvals
  • Full audit log per environment
  • Rollback is a button, not a prayer
The IDE

Query, browse, visualize. Across every dialect.

Connect to PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite, MongoDB, Redis, Cassandra, Neo4j, Elasticsearch, ClickHouse, CockroachDB, and TimescaleDB from one tool. Same keyboard shortcuts, same tabs, same workflow.

  • Monaco-powered SQL editor with autocomplete and syntax highlighting
  • Multi-tab queries with persistent history
  • Visual schema explorer with on-demand DDL
  • Result-set charts (bar, line, pie) without leaving the page
  • Saved queries and shared snippets
  • Execution plan viewer for query tuning
The Change Manager

Move schema changes through environments. Safely.

Bundle versioned scripts into releases. Route them through your team’s approval policy. Promote across dev, staging, and production with full audit and rollback.

✓

Versioned scripts

Every change is a tracked script with target connection, environment, and dependency order.

⇄

Approval gates

Multi-signature policies per environment. Production deploys are gated on your approval policy.

↺

Rollback

Release manifests carry their own revert paths. Recovery is one action, not an incident.

⌕

Discovery

Scan your network for unmanaged databases. Bring shadow infrastructure under control.

⇣

Repo integrations

Pull scripts from GitHub, GitLab, Bitbucket, Azure Repos, or AWS CodeCommit.

⏱

Execution history

Per-release status, timing, and output preserved with full audit log.

Built on the “Fleet of One” principle

Whether you manage one database or thousands, the workflow is identical. No separate “single” vs “fleet” modes. No re-platforming when you grow.

One developer

Replace your standalone IDE. Get change tracking, approvals, and audit out of the box.

One platform team

Centralize connections, gate production access, run schema reviews in the tool your devs already use.

One enterprise fleet

Discovery, inventory, fleet-wide changesets, identity federation (SAML/OIDC/LDAP), full audit retention.

Frequently asked questions

Answers to what teams ask before they join the beta.

Which databases are supported?
PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite, MongoDB, Redis, Cassandra, Neo4j, Elasticsearch, ClickHouse, CockroachDB, and TimescaleDB are supported today with native adapters for the IDE and (where applicable) the change manager. Additional dialects are added on a rolling basis through the beta based on cohort demand.
Can I self-host Simcha DB Studio?
Yes, and self-hosting is the only deployment model, on every tier, not an Enterprise-only option. Simcha DB Studio ships as a single container you run in your own environment (Docker, ECS Fargate, or Kubernetes, on any cloud or on-prem), so your data never leaves your perimeter. That is exactly why it fits regulated industries like healthcare, financial services, and the public sector. There is no Simcha-managed SaaS; the only Simcha-hosted environment is the beta sandbox.
Is there a free tier?
During the private beta, every cohort member gets full product access at no cost. When commercial plans open at general availability, there will be a free tier suitable for single developers with a small number of connections, plus paid tiers for teams that need approvals, audit, SSO, and self-hosting.
When will Simcha DB Studio be generally available?
We’re rolling out the private beta in waves throughout 2026. Beta participants help shape the GA roadmap, receive founding-customer pricing when commercial plans open, and have direct access to the team building the product.
private beta

Help us ship the right product.

Beta participants get a hosted sandbox with sample databases pre-loaded, the IDE plus the Change Manager workflow, and a direct line to the team. We trade product access for honest feedback that shapes what ships at GA.

What you get

  • Hosted sandbox at beta.simchadbstudio.com, no install
  • Sample databases pre-loaded so you see it work in seconds
  • Connect your own (non-production) databases if you want
  • A "Report an issue" button in the app to send feedback straight to the team
  • Early access to new features as they ship

Request beta access

30 seconds. We reply within 1-2 business days.

Got it. We’ll review and email you within 1-2 business days with next steps.

We’ll only use this info to evaluate your beta request and follow up. We won’t share or spam.