Developer
Services, deployments, and logs.
Reads stay on. Writes can be turned off anytime. Sends still wait for your approval in chat.
Read
Read data from Railway.
Write
Create, update, or send in Railway.
Individu watches these and starts a chat when something needs your attention.
A regular-environment Railway deployment fails, crashes, or recovers.
What Individu can do once this integration is connected.
DESTRUCTIVE: Commits all staged changes in a Railway environment and triggers a deploy.
Attach a source to an existing service: a GitHub repository (deploys on push, builds immediately) or a Docker image.
Create an S3-compatible object storage bucket in a project and provision it in an environment.
Create a new service from a GitHub repository and trigger its first deployment.
Create a Railway Function: a service that runs one file of TypeScript on the Bun runtime, with no repository, Dockerfile or build step.
Create a new Railway project.
Create a new service in a project from a Docker image, or an empty service to configure later (e.g.
Expose a service on the public internet over a raw TCP port (e.g.
Create a persistent volume in a project and optionally attach it to a service at a mount path.
Create a project webhook: Railway POSTs a JSON payload to the URL whenever one of the chosen deployment, monitor or volume-alert events happens in the project.
Permanently delete an object storage bucket and its contents.
Remove a domain from a service: a Railway-generated *.up.railway.app service domain or a custom domain.
Delete a project-scoped feature flag. Workspace-scoped flags cannot be deleted from project context.
Permanently delete a service: its deployments stop and are removed, along with its domains, variables and deployment triggers.
Remove a service's TCP proxy, taking its public endpoint offline.
Permanently delete a volume and its data.
Delete a project webhook so Railway stops POSTing to its URL.
Deploy a Railway template into a project — a database (postgres, mysql, redis, mongo), a clustered high-availability database, or an application template.
Inventory of everything in a Railway environment — services, volumes, buckets, shared variable names — with staged changes applied.
Everything about one service in an environment: its config with staged changes applied (source, build, deploy, networking, volume mounts), the per-field staged changes pending on it, mounted volumes, live domains and TCP proxies, the latest deployment, and its tracing state.
Read one Railway template: its name, description, README, the services it creates, every env-var input it takes (which are required and which are optional), and — for clustered database templates like postgres-ha — the HA topology counts deploy-template can size.
Get detailed status for one domain on a service, by hostname, URL, or domain ID: required DNS records and whether they currently match, ownership verification, certificate status, and any certificate error.
Health overview of every service in an environment in one call: current LIVE (settled) deployment state, replica status, recent failures, unresolved warnings/criticals, and cron execution results.
Fetch the full markdown content of a Railway documentation page by URL or slug (e.g.
Expose a service publicly. Without `domain`, generates a Railway *.up.railway.app service domain (if the service already has domains, they are returned instead of creating another).
Get the S3-compatible connection details for a bucket in an environment: endpoint, bucket name, region, URL style, access key and secret.
Get the AI-generated diagnosis for a failed deployment: root cause category, analysis, and suggested fixes, along with deployment context (service config, source repo, branch, commit, PR, failure stage and error).
Get a Railway feature flag (Signal) by name for a project or its parent workspace scope.
Get a Railway Function's source code and runtime in an environment.
Get logs from Railway — deploy (runtime), build, http (proxy request), network-flow (per-connection egress/ingress) and dns (name lookups) streams.
Prefer describe-service: it applies the staged changes onto the live config for you and adds mounted volumes, domains, TCP proxies and the latest deployment.
Get resource usage metrics (CPU, memory, disk, network) for a service, summarized as current/average/min/max over a time window.
Show the changes staged in a Railway environment that accept-deploy would commit: per resource (service, volume, bucket, group) the action — create, delete, update — and each changed field with its live and staged value.
Prefer describe-environment: it also lists services that exist only in the staged patch, unattached volumes, and each resource's staged state.
Get the spans of one distributed trace, as a tree from the edge down through every service that handled the request.
Read the tracing settings of an environment's services: whether each is traced and its auto-instrumentation switch.
Report what one service's own instrumentation covers: the spans its app exported in the window, by span kind, by the remote system they name (database, cache, queue, RPC or HTTP client) and by the instrumentation library that emitted them.
Get the HTTP error rate for a service over time — the share of requests answered with a 5xx.
Get HTTP request counts for a service, bucketed over time and split by response status class (2xx/3xx/4xx/5xx).
Get HTTP latency percentiles (p50, p90, p95, p99) for a service, bucketed over time, in milliseconds.
List the account's beta features: whether the user is in Priority Boarding (Railway's beta programme, which auto-enables new beta features) and every beta feature they may turn on or off, with its current state.
List recent deployments for a Railway project, optionally filtered by environment, service, or status.
List all domains (Railway-generated service domains and custom domains) for a service in an environment.
List Railway feature flags (Signals) for a project and optionally the parent workspace.
List all Railway projects accessible to the authenticated user.
List the ids and names of all services and environments in a Railway project.
List the TCP proxies exposing a service over the public internet on a raw TCP port (e.g.
List distributed traces of an environment, newest first — one row per request that has at least one span matching the filter.
List all environment variables for a service, fully rendered (reference variables like ${{Postgres.DATABASE_URL}} are resolved).
List a project's webhooks: for each, the URL Railway POSTs to, the deployment, monitor and volume-alert events that trigger it, whether it covers preview (PR) environments, the...
List the Railway workspaces the current user belongs to.
Purge the CDN cache of a service right now, so every edge node refetches from the service on the next request.
Hand a multi-step task in one project environment to Railway's own AI agent, for work too open-ended for the direct tools: investigating a failing deploy across services, or planning and making a set of related changes.
Re-run the most recent deployment of a service in a given environment, reusing that deployment's existing build.
Regenerate the S3-compatible credentials for a bucket in an environment and return the new ones.
Restart a service's running deployment in place — the containers restart without rebuilding the image, and no new deployment is created (use redeploy for a fresh build copy).
Request a new TLS certificate for a custom domain whose issuance failed.
Search the Railway documentation (docs.railway.com) for features, configuration, guides, and tutorials.
Search the Railway template marketplace by name, description or keyword — databases (postgres, mysql, mongo, redis, clickhouse), their high-availability variants, and application templates.
Turn an account beta feature on or off for the current user.
Create a project-scoped feature flag or update its default value, optionally replacing its targeting rules.
Enable or disable tracing and auto-instrumentation for one service in one environment, each independently.
Set one or more environment variables on a service (or environment-wide shared variables when serviceId is omitted).
POST a sample event payload to a URL and report the HTTP status it answered with, to check a webhook endpoint before creating or after updating a webhook.
Rename a bucket. The name is project-wide (not per environment) and takes effect immediately.
Repoint or rename an existing domain on a service.
Replace a Railway Function's source code.
Update a service's configuration: build/start/pre-deploy commands and pre-deploy timeout, builder, healthcheck, sleep mode, root directory, cron schedule, Dockerfile path, restart policy, config file path, watch patterns, replicas per region, resource limits, deployment overlap/draining, outbound IPv6, the private network endpoint name, tracing (edge tracing and eBPF auto-instrumentation) and cdn (edge caching of the service's public domains).
Update a volume's name, mount path, or which service it is attached to.
Change a project webhook's URL, the events that trigger it, or whether it covers preview (PR) environments.
Get the current authenticated Railway user's profile information.