Self-hosting
Self-hosting
Run the open-source platform with your own infrastructure and provider credentials.
On this page
What is open source
The official repository contains the platform, API, workers, CLI, SDKs and public skill. The separate hosted marketing website is maintained privately. Self-hosting uses your own provider accounts and infrastructure; provider usage may still cost money.
Start with the repository
Follow the repository’s current self-hosting instructions and environment example. The supplied Compose stack includes the Supabase services, database, workflow engine, storage and application services. A bare database is not enough.
git clone https://github.com/gitroomhq/agent-media-app.git
cd agent-media-app
cp .env.example .env
# Configure your provider keys and deployment settings in .env
docker compose upConfigure the deployment
Keep provider keys and service credentials on the server. Read the environment example for supported replacements, then check database migrations, API health, worker connectivity and storage access before allowing traffic.
Enable temporary uploads deliberately
Temporary upload storage must be private and enforce the application expiry. Configure the dedicated bucket and lifecycle cleanup using the OSS deployment guide. Do not expose storage credentials to the upload panel.
Hosted credits and self-hosting
Self-host billing configuration is separate from the hosted Agent Media account. Turning off application billing does not make provider generation free or award hosted credits. Review your provider billing before running jobs.