Self-host AgentLaunch on Railway

What you get#

The Self-Host License gives you the full AgentLaunch source code: the web app, the launch agent, the Chrome extension and the directory catalog. You run it on your own Railway account, with your own AI key. Every account on your copy gets unlimited launches.

• $149, paid once. No subscription.
• A private GitHub repository with the code and a setup guide.
• Directory catalog updates about every three months, for as long as AgentLaunch is maintained.
• Use it for your own products, or to run launches for your clients.

Railway is the only platform we support. The app is a standard Node.js server, a Postgres database and a static site, so it can run elsewhere, but you would be on your own.

What you need#

Optional: a Plunk account for email alerts and password resets, and a Composio key if you want AgentLaunch to read directory verification emails from Gmail. You don't need any email service to sign up or log in.

Get access to the code#

1. Buy the Self-Host License on the pricing page.
2. Log in to agentlaun.ch and open your Account page.
3. Enter your GitHub username and click Send invite.
4. Accept the invitation from GitHub (check your GitHub notifications or email).
5. Clone the repository to your computer.

One license covers one GitHub account. If you switch to a different account on the Account page, the old one loses access.

1. Install the tools#

npm install -g @wasp.sh/wasp-cli@0.25.0
npm install -g @railway/cli
railway login

2. Create the Railway project#

Run these from the root of the repository. They create a project with a Postgres database, a server and a site, and give both a public address.

railway init --name agentlaunch
railway add --database postgres
railway add --service agentlaunch-server
railway add --service agentlaunch-client
railway domain --service agentlaunch-server --port 8080
railway domain --service agentlaunch-client --port 8080

The two domain commands print your server address and your site address. Write them down; you need both in the next steps.

3. Configure the server#

Generate two secrets, then set the server's variables. Replace every value in angle brackets.

openssl rand -hex 32
openssl rand -hex 32

railway variables --service agentlaunch-server \
  --set 'DATABASE_URL=${{Postgres.DATABASE_URL}}' \
  --set 'PORT=8080' \
  --set 'AGENTLAUNCH_SELF_HOSTED=true' \
  --set 'WASP_SERVER_URL=<server address>' \
  --set 'WASP_WEB_CLIENT_URL=<site address>' \
  --set 'JWT_SECRET=<secret 1>' \
  --set 'JEV_KEY_ENCRYPTION_SECRET=<secret 2>' \
  --set 'ADMIN_EMAILS=<your email>' \
  --set 'ROCKET_LAUNCH_SUBMISSION_AGENT_ENABLED=true' \
  --set 'ROCKET_LAUNCH_TEXT_AI_BASE_URL=https://openrouter.ai/api/v1' \
  --set 'ROCKET_LAUNCH_TEXT_AI_MODEL=openai/gpt-4.1-mini' \
  --set 'ROCKET_LAUNCH_TEXT_AI_API_KEY=<your OpenRouter key>'

openai/gpt-4.1-mini is the model AgentLaunch is tested with. Other models that support tool calls should work, but results vary.

4. Deploy#

SERVER_URL=<server address> SITE_URL=<site address> ./selfhost/deploy.sh

The first build takes several minutes. When the server starts it sets up the database and loads the directory catalog in the background, which takes about a minute.

5. Log in and connect Chrome#

1. Open your site address and click Sign up.
2. Use the email you set in ADMIN_EMAILS. You're logged straight in; there is no email to confirm.
3. Open Connect, download the extension, unzip it, and load it on chrome://extensions with Developer mode on.
4. Click Connect Chrome on the same page and confirm the prompt.
5. Go to Dashboard, click Launch a product, and paste your product's website.

Add teammates#

Your copy has no verification emails, so only approved addresses can create an account. Admins in ADMIN_EMAILS are always allowed. Add anyone else with SELF_HOST_ALLOWED_EMAILS, as a comma-separated list. An entry like *@youragency.com allows a whole domain.

railway variables --service agentlaunch-server \
  --set 'SELF_HOST_ALLOWED_EMAILS=alex@yourcompany.com,*@youragency.com'

Every account launches on your AI key with no limit, so only approve people you trust.

Use your own domain#

1. In the Railway dashboard, open agentlaunch-client, go to Settings, then Networking, and add your domain.
2. Point your DNS at Railway as it shows you.
3. Set WASP_WEB_CLIENT_URL on agentlaunch-server to the new address.
4. Deploy again with SITE_URL set to the new address.
5. Download the extension again from Connect on the new domain. Each download is set up for the site it came from.

Optional: email alerts and Gmail#

Updates#

We publish a new release with updated directory data about every three months. To update your copy:

git pull
SERVER_URL=<server address> SITE_URL=<site address> ./selfhost/deploy.sh

Database changes and the new catalog apply when the server restarts. If the release notes say the extension changed, download it again from Connect and reload it in Chrome.

Troubleshooting#

License in plain words#

• You can run it on as many servers as your organization needs, change it, and rebrand it.
• You can launch your own products and run launches for your clients, as long as you operate it yourself.
• You can't resell or share the code, or offer it as a product other people log in to.
• You can't publish the directory catalog or playbooks as a list or dataset.

The full license is in LICENSE.md in the repository. Questions go to support@agentlaun.ch.