| title | Installation |
|---|---|
| description | Install Studio with the public CE runtime paths or use the published images in your own deployment |
ShipSec Studio has three public setup paths:
Best for:
- contributors
- source-level debugging
- local product development
git clone https://github.com/ShipSecAI/studio.git
cd studio
just init
just infra up
just devThis keeps the backing services in Docker and runs frontend, backend, and worker from source with PM2.
Best for:
- validating the public CE deployment path
- running the product on one machine without a source workflow
- smoke testing the published repo end to end
git clone https://github.com/ShipSecAI/studio.git
cd studio
just ce upThis brings up infra plus frontend, backend, and worker in Docker.
Best for:
- self-hosting
- running Studio on your own infrastructure
- building your own runtime model around the published images
The public repo publishes the Studio application images. Pair them with the required backing services described in Self-Hosting.
Requirements:
- Bun
- just
- Docker
- Docker Compose
Start:
just init
just infra upThis installs dependencies and creates:
backend/.envworker/.envfrontend/.env
Start:
just devThe public repo now ships a minimal CE runtime stack for local source development:
docker/docker-compose.infra.ymlfor shared servicesdocker/docker-compose.apps.ymlfor the full Docker app overlay
See Development / Multi-Instance Dev for contributor-oriented local instance details.
just ce upThis uses:
docker/docker-compose.infra.ymldocker/docker-compose.apps.yml
The default frontend URL is http://localhost:5173 and the default backend URL is http://localhost:3211.
SECRET_STORE_MASTER_KEY
CHAT_AI_MODEL_IDCHAT_AI_BASE_URLCHAT_AI_API_KEY
Configure only what you actually plan to use:
- GitHub
- AWS
- GCP
- Slack
- Jira
The open-source model is direct configuration, not hosted indirection.
just dev applies the committed repo migrations before starting the app
services. If your environment layers in extra migration directories, those are
picked up by configuration rather than being hardcoded into the public repo.
In the source-development path, just dev also creates the active instance
database automatically when the local CE Postgres container is running.