Where to go
Five places you can open. This list makes no claim about whether each is up: a page on one origin cannot measure the others, because to script a cross-origin failure and an outage are the same event. Service status is its own tile for that reason.
-
Workbench
app.nucleora.org
Design, edit and analyse constructs. Sign in happens here.
-
API reference
info.nucleora.org
Every endpoint, its method, its scope, and an FAQ that answers what the API does not do.
-
Administration
admin.nucleora.org
Users, licences, teams and labs. Lab owners see only their own.
-
Codebase documentation
information.nucleora.org
How the codebase works, end to end, with annotated tours of the real source.
Password-gated.
-
Service status
status.nucleora.org/status
Live checks across the network.
Linked at /status: the root of that host returns a plain-text pointer, not a page.
Services behind them
These answer programs, not browsers, and return JSON rather than a page: api.nucleora.org (the public API; keys, scopes and revocation), auth.nucleora.org (sign-in and sessions), storage.nucleora.org (projects and versions) and collab.nucleora.org (the real-time collaboration room). Opening one in a browser correctly gives you an authentication error; that is the service working.
Your network
Each panel names the route it reads and states which condition it is in — live, empty, built but not deployed, not built yet, route absent, refused, unreachable, or an unexpected response. A panel never shows a figure it did not measure: where no count came back you will see an em dash, not a zero.
This network, measured
Each figure is produced by a command against this repository, shown next to it.
What this is
A working environment for nucleic-acid construct design: sequence editing and annotation, codon and expression work, CRISPR guide design and off-target scoring, mRNA and vaccine constructs, assembly planning, and the reference data behind all of it. It runs as a network of hosts rather than one application, so administration, documentation and the public API are separate surfaces sharing one account. Sign in or register to turn this page into your own network view; for anything else, get in touch.
Capability areas, sized by route count
The largest namespaces in the backend route table, counted from the imported application at build time rather than asserted. A namespace with no recorded description is still listed.
This network, measured
Every figure here is derived by a command against this repository, and the command is printed with it. None of these numbers is typed into this page.