DbState Private Beta

Evaluate DbState with a real PostgreSQL workflow.

The DbState Private Beta is for developers, database engineers, and technical teams that want PostgreSQL database state in Git without handing database execution or Git history to the tool.

Review the application questions Explore the Product

PostgreSQL. Windows. Local workflow. Access by request.

Current scope

A focused local workflow.

Private Beta scope is intentionally narrow: PostgreSQL state, local Windows workflows, repository desired state, and review-only release handoff.

Platform

Windows
Local service
Browser-based interface
Local developer workflow

Database

PostgreSQL
Saved non-secret connection profiles
Password entered when needed
PostgreSQL passwords are not stored

Repository

Existing or newly initialized local Git repository
Repository desired state under controlled DbState folders
Database objects stored as files
Reference data stored as YAML
Git commands remain user-controlled

Review workflow

Schema Compare
Object Diff
Reference Data Diff
Release Plans
Review-only release artifacts

execution boundary

Database execution remains outside DbState.

Participant fit

Private Beta is for teams with a real database-change problem.

DbState is currently best evaluated by teams that already feel the cost of scattered database state, difficult review, or unclear handoff between repository changes and PostgreSQL.

Application developers

Managing database changes beside application code and pull requests.

Database engineers

Comparing target PostgreSQL databases with repository desired state.

Technical leads

Trying to reduce undocumented manual changes and scattered release scripts.

Regulated or audit-sensitive teams

Seeking clearer database-state history, review evidence, and controlled handoff without claiming compliance certification.

Evaluation environment

What you need to evaluate DbState.

A useful Private Beta evaluation needs a real PostgreSQL workflow, a local repository for desired state, and a controlled environment where inspection and repository writes are appropriate.

Required

needed for evaluation

Windows development machine
Local or reachable PostgreSQL database
Git installed
A local Git repository for desired database state
Permission to inspect the selected PostgreSQL database
Permission to write files into the local repository
A non-production or otherwise safely controlled evaluation environment

Bring a workflow that exposes the problem.

A useful evaluation starts with a workflow that is already difficult to review, reproduce, or hand off safely.

01

Capture an existing database into Git

Use Database-to-Repository Schema Compare to capture selected PostgreSQL objects as durable files.

02

Compare desired state with a target database

Use Repository-to-Database Schema Compare to identify different, missing, database-only, and in-sync objects.

03

Version reference data

Select a lookup or configuration table, define row identity, and capture it as repository-managed YAML.

04

Review row-level differences

Compare repository-managed reference data with PostgreSQL through Data Diff.

05

Build a Release Plan

Select supported schema candidates and inspect the review surface before any database execution occurs outside DbState.

Evaluation should focus on real comparison, review, and handoff behavior rather than assuming every selected candidate will produce an artifact.

Access package

What Private Beta access includes.

Private Beta access gives participants enough product context to evaluate the current Windows build against a real local PostgreSQL workflow.

Included with access

private beta access

Access to the current Windows build
Private Beta installation instructions
Getting-started guidance
Current known limitations
Product workflow documentation
A channel for structured feedback
Early visibility into product decisions that affect local PostgreSQL workflows

Feedback expectations

What we need from participants.

The most useful Private Beta feedback is grounded in real schema, reference-data, comparison, and release-review problems.

Feedback requested

structured feedback

A real PostgreSQL workflow to evaluate
Honest feedback about usability and terminology
Reports of parsing, comparison, or workflow failures
Clear reproduction steps when possible
Feedback on schema and reference-data coverage
Feedback on Release Plan and review boundaries
Confirmation when product language is ambiguous or misleading

Known boundaries

Controlled scope, not hidden scope.

Private Beta scope is intentionally bounded so DbState can focus on local PostgreSQL state review without implying hosted collaboration, direct execution, or automatic Git behavior.

Included

current beta

Local Windows workflow
PostgreSQL inspection
Explicit repository capture
Read-only Repository-to-Database comparison
Object Diff
Data Diff
Release Plans
Review-only release artifacts
User-controlled Git operations
No stored PostgreSQL passwords

Not included

outside current beta

Direct database apply
Generated SQL execution
Automatic Git add, commit, push, pull, fetch, or tag
Hosted collaboration
Shared server workspaces
Organization approval workflows
Hosted audit trails
Automatic rollback
macOS and Linux builds
Database engines other than PostgreSQL

Application questionnaire

Private Beta application questions.

The questionnaire can be reviewed, but submission is not currently available. Nothing entered is transmitted to DbState while application intake is closed.

Contact

Namerequired

Work emailrequired

Company, team, or projectrequired

Rolerequired

Technical environment

PostgreSQL version or versionsrequired

Windows versionrequired

Other database engines currently used

Git hosting or repository workflow, when applicable

Current workflow

How are PostgreSQL schema changes managed today?required

How is reference data managed today?required

Who reviews database changes?required

How are release SQL scripts prepared and executed?required

Evaluation problem

Describe the last database change that was difficult to review, reproduce, or release.required

Which DbState workflow would you evaluate first?required

Which PostgreSQL object types matter most?required

Do you manage reference-data tables through Git today?required

What would make the Private Beta evaluation useful?required

Consent

I consent to DbState using this information to evaluate my Private Beta application and contact me about the application.required

I would also like occasional updates about DbState.

intake closed

No information entered on this page is transmitted to or stored by DbState while application intake is closed.

Intake status

Application intake is currently closed.