Environments
Skynet runs two deployment tiers — production on the canonical
skynetgo.org domain, and your local dev stack. Pick the
right base URLs for what you're targeting.
Production
| Service | URL |
|---|---|
| Public API | https://api.skynetgo.org |
| Auth | https://auth.skynetgo.org |
| Sky-node gateway | https://node.skynetgo.org |
| Web app | https://skynetgo.org |
Production is the live deployment serving real users and real observations. Be deliberate about what you submit.
Local dev
| Service | URL |
|---|---|
| Public API | http://127.0.0.1:5001 |
| Sky-node gateway | http://127.0.0.1:5002 |
| Auth | http://127.0.0.1:5000 |
| Web app | http://127.0.0.1:4200 (React) |
For local development. Stand up the Docker compose stack from
infra/docker/ — see
infra/docker/README.md for
the full set of services.
CORS allow-list
The public API allows browser requests from the origins listed in
apps/public-api/public_api/main.py
(at the CORSMiddleware configuration). The active list includes:
https://skynetgo.org,https://www.skynetgo.orghttps://auth.skynetgo.org,https://api.skynetgo.org- Various
127.0.0.1andlocalhostorigins on common dev ports.
If you're building a browser-side integration that needs to be embedded elsewhere, file a request to add the origin — the allow-list is hand-curated.
Health checks
Each backing service exposes liveness/readiness endpoints — useful for monitoring and for confirming a deployment is up before pointing clients at it:
GET /healthz— basic liveness.GET /readyz— ready to accept traffic (DB + Redis + object store reachable).
The dependencies covered are at
packages/py/skynet-db/skynet_db/health.py.