DDD Studio is currently in closed alpha. Signing in with Google or GitHub counts as your application to join. Please note that applying does not guarantee access.

For organisations

Run DDD Studio on your own infrastructure.

The same product as our demo system, delivered as one container image. Your models stay in your database, and your people sign in through your identity provider.

What you get

One image

Backend and web app in a single signed container, served from one origin.

Your identity provider

Sign-in through any OpenID Connect provider, for example Keycloak.

Your data

Models live in your own PostgreSQL.

What you need

Runtime
Any container platform: Kubernetes, Docker, a virtual machine
Database
PostgreSQL, optionally with your own CA and connection pool settings
Sign-in
An OpenID Connect identity provider
Network
One HTTPS origin for the web app, the API and the MCP endpoint

How it runs

Your people
Browser and MCP agents
Your cluster
DDD Studio image
Your database
PostgreSQL

Sign-in goes to your OpenID Connect provider; the database and the provider stay on your side.

Technical details

Besides the web app and the API, the image serves the MCP endpoint at /mcp, so agents connect to your instance the same way as to our demo system. Database migrations run when the container starts.

Sign-in goes through your OpenID Connect provider. You can restrict access to members of a group, and grant the administrator role by group membership. There is no consent checkbox for terms that are not yours.

The user documentation ships inside DDD Studio and always describes the version your instance runs.

Let's talk about your setup.

Tell us a little about your team and your platform, and we will get back to you.