Railway
Services and deploys, no app code required.
Railway already knows what's running. Neat just asks it — services, deploys, and the traffic between them, fused straight into the graph.
Paste it into your coding agent — it runs the full setup with your credentials.
Set up NEAT's Railway connector so the graph shows real service-to-service traffic in my Railway project — including private-network calls no repo declares. It pulls Railway's HTTP logs and network-flow logs. Steps:
1. Ensure NEAT is running for this repo.
2. Gather a Railway API TOKEN (railway.app account settings -> tokens; export as RAILWAY_TOKEN, don't paste inline), my ENVIRONMENT ID and the SERVICE ID to observe (from the Railway project/service URLs or the `railway` CLI), and a service-name-by-id map { "<serviceId>": "<name in my graph>" } so flow-log peers resolve to named services.
3. Run: npx neat.is connector add railway --token $RAILWAY_TOKEN --environment-id <env> --service-id <svc>
Then add the serviceNameById map to this entry's options in ~/.neat/connectors.json, or answer the prompts.
4. Restart the daemon to begin polling.
5. Verify: generate traffic, then check the graph for OBSERVED route CALLS onto the service and CONNECTS_TO edges between services from the flow logs. Report any service quietly calling another's internal API — traffic the codebase alone wouldn't show. how it works
See the service call that only exists at runtime — the one no repo declares.
- Point Neat at your Railway project — neat connector add railway.
- Neat pulls every service, deploy, and the private-network traffic between them.
- Your agent finds a service quietly calling another service's internal API directly — traffic no codebase alone would ever show.
