Quickstart

One-click deployCopy Anchor Link

Open the template and keep its defaults. Railway generates the credentials and configures the service references. Review Configuration and Cost, then confirm your deployment in Railway.

Open your installationCopy Anchor Link

1. Wait for gateway to become healthy in Railway. If startup fails, inspect the failed service's logs before retrying.
2. Open the Gateway public URL.
3. In web → Variables, read ADMIN_EMAIL and the generated ADMIN_PASSWORD. Use them to log in. Keep them private.
4. Create your organization and project. If the organization flow is not shown, open /organizations/new/ on your installation.
5. Open Settings → Projects → Client Keys (DSN). Copy the public key and project ID.

Startup performs initialization and migrations. There is no measured deployment-time promise. Do not run concurrent manual migrations while bootstrap is running.

Connect an applicationCopy Anchor Link

Set SENTRY_DSN on an application service in the same Railway environment. Replace the symbolic public key and project ID with your project's values:

SENTRY_DSN=http://PUBLIC_KEY@${{gateway.RAILWAY_PRIVATE_DOMAIN}}:8081/PROJECT_ID

Port 8081 is the private SDK listener. The public interface uses port 8080 and rejects ingestion. These values come from Gateway configuration and the template README.

Keep your actual DSN in environment variables, not source files. A local shell using railway run still cannot reach Railway's private network.

Verify deliveryCopy Anchor Link

Run an included Node, Python or Go example from the connected application environment. Select the same project and environment in Sentry, then check:

• Issues for Railway error example.
• Logs for Railway structured log.
• Traces for railway-example, with a child span under its parent.

An SDK flush only confirms transport completion. Verify indexing in each view. If data is missing, use Troubleshooting.

Before relying on the installationCopy Anchor Link

Review Configuration and variables, Cost and the coordinated backup procedure in Upgrades. Persistence is not a backup.