Historically, the Cytognosis frontend was statically compiled and hosted on Google Cloud Storage buckets (e.g. gs://cytognosis).
cytognosis/website repository executes entirely via a fully Serverless Google Cloud Run container footprint.us-central1Deployments are fully automated under the Cytognosis GitHub organization.
Instead of provisioning long-lived, high-risk JSON service account keys, GitHub Actions authenticates to Google Cloud via short-lived OIDC tokens.
cytognosis/website)website-deployer@cytognosis-infrastructure.iam.gserviceaccount.com| Registry Area | Purpose | Status |
|---------------|---------|--------|
| cytognosis-website-v2 | Holds immutable builds of the main platform web server | Active |
| cytognosis-compute | Standardized Jupyter data science environments | Active |
| neo4j | Containerized graph mappings for Molecular Medical NLP | Active |
| cal.com | Internal HIPAA-managed appointment scheduling proxy | Active |
When validating architecture locally, developers bypass Docker compose for rapid frontend traversal:
``bash1. Update packages
uv sync
Note: All local deployments simulate cloud data architectures natively via SQLite (database.db`), guaranteeing schema 1:1 mirroring prior to Cloud SQL production synchronizations.