Get Divengine Studio
Studio is not a service you sign up for. It is free software you download and run on your own infrastructure: a laptop to try it, a server for your team, your cloud of choice. Your data never leaves it.
What you need
| Component | Version | Notes |
|---|---|---|
| PHP | 8.4 | With pdo_pgsql, gd, xml, mbstring, curl, zip, opcache. |
| PostgreSQL | 14 or newer | With the pg_trgm extension. Studio is developed and tested on PostgreSQL. |
| Composer | 2.x | Downloads Drupal core, contributed modules and libraries. |
| Web server | any | Caddy, nginx or Apache with PHP-FPM. |
| Git | any | To get the code, and for Code Source to read your repositories. |
Install in five steps
Get the code
git clone https://github.com/divengine/studio.git cd studio composer installCreate the database
sudo -u postgres psql <<'SQL' CREATE ROLE studio LOGIN PASSWORD 'choose-a-good-one'; CREATE DATABASE studio OWNER studio; \c studio CREATE EXTENSION IF NOT EXISTS pg_trgm; SQLPrepare the private files folder
Test evidence and attachments are private: tell Drupal where they live before installing.
cp web/sites/default/default.settings.php web/sites/default/settings.php mkdir -p private/files echo "\$settings['file_private_path'] = '../private/files';" >> web/sites/default/settings.phpRun the recipe
One command installs Drupal, every Studio module, the Studio theme, the roles and the default configuration.
vendor/bin/drush site:install recipes/divengine_studio \ --db-url=pgsql://studio:choose-a-good-one@localhost/studio \ --account-name=admin --site-name='Divengine Studio'Point your web server at
web/and log inCreate your first Development, invite your team and give each person a role. Optionally apply the MCP recipe to connect AI assistants.
Packaging is evolving: container images and other ways to install are on the roadmap, always as software you run yourself.
What the recipe gives you
The whole suite
Artifacts, traceability, BPMN and UML modelers, Unified Process, test management, projects, timesheets, knowledge base, discussions, code source and database schemas.
Roles that make sense
Content editor, Project Manager, QA User, Tester, Lead and Manager, Studio Manager, Database analyzer.
Sensible defaults
Artifact types and lifecycles, trace types, process definitions, development cases and QA settings, ready to adapt.
A real Drupal site
Extend it with modules, theme it, integrate it through JSON:API. Studio follows Drupal's own practices.
Optional MCP server
A second recipe adds a read-only MCP endpoint with token authentication for AI assistants.
GPL-3.0
Free software: use it for any purpose, study it, change it and share your improvements.
Need a hand?
The documentation walks you through installation, configuration and every feature, in plain language.