Service status

ContextDB Cloud service status.

Honest component states for the hosted service. No uptime percentages or incident history are published yet. There is no measured service history to report. When there is, this page will report measured reality, not aspirations.

Availability by component

Components

Component State Notes
Python SDK (pycontextdb) Available Version 0.4.4 on PyPI. Includes partition-scoped high-cardinality recall, explicit Memory Evolution, and an eval-locked trust model. License and self-hosting details are on the Open source page.
Data-plane gateway (api.contextdb.ai) Cloud Public HTTPS ingress with project-key authentication in a single process. No availability SLA.
Console (app.contextdb.ai) Cloud Public self-serve sign-in with human sessions via BFF. No availability SLA.
OAuth MCP connector Hosted Alpha Six tools over stateless Streamable HTTP with OAuth 2.1 PKCE, rotating refresh tokens, project consent, server-bound user partitions, and revocation. Official MCP Registry io.github.atomsai/contextdb-memory@0.1.0 is published. Cursor completed production OAuth and displayed the generated tool list on September 24, 2026. On September 25, 2026, Cursor invoked remember, recall, action recall, confirmation, and forgetting end to end. On September 30, 2026, the ContextDB listing on Cursor Directory went public and the ChatGPT plugin entered OpenAI review. Cursor's manual-approval prompt for forgetting, the remaining named-client proofs, and the OpenAI and Anthropic directory reviews remain open.
Memory Evolution Cloud Public /v1/evolve, Console lineage, operation-aware Formation, and evidence-ID Memory CI. Bounded functional proof passed, with no scale, failover, availability, or SLO claim.
Asynchronous Formation Hosted Alpha Public submit/poll API with durable encrypted PostgreSQL jobs, leases, and recovery. One separate single-instance Formation process runs on the gateway's app VM.
Hosted Memory CI Hosted Alpha Live Console and four /evals/v1 operations. Uses a durable PostgreSQL queue, leases, bounded recovery, cancellation, pinned baselines, and content-free exports. One separate single-instance Evals process runs on the same app VM.
Memory CI public distribution Available contextdb-memory-ci==0.1.0a1 published through trusted publishing with attestations and verified from a fresh isolated registry install. Reusable Action tag and prerelease are public. The Action installs that exact package. The strict contract and CLI source remain public. Distribution status does not change hosted-service maturity.
Managed Sources Private Alpha Postgres has bounded operated proof. Supabase has a protocol path. BigQuery has bounded synthetic provider proof from 2026-08-26. Snowflake and Databricks have no-network contract tests only. There is no customer warehouse proof or public access. The design-partner gate is open.
Google and GitHub login Staged Security implementation is deployed. Production provider credentials are not configured.
Public Cloud clients Available Python 0.2.0a2, TypeScript 0.2.0-alpha.2, OpenAPI, and five framework starters. Hosted Formation, Memory CI, and Managed Sources remain scoped on this page.
Signed backups and restore drill Operated Alpha Daily CMEK-protected PostgreSQL + SQLite bundle and weekly disposable-cluster content drill. Exact signed bundles passed on August 24 and September 21. There is no PITR, role/secret recovery, failover, published recovery objective, or complete disaster-recovery claim.
Marketing site (contextdb.ai) Cloud Public, static, tracker-free, and claim-gated
Image CDN (cdn.contextdb.ai) Cloud GCP Cloud CDN with versioned immutable image assets.
Active-profile metering and pricing Staged / Shadow Organization-deduplicated monthly counts and pricing previews are staged and not charged. No Stripe exports occur until operated proof is complete.
Enterprise controls (SSO/SCIM, residency) Planned Not implemented and not claimed.
Worker recovery was tested in August 2026. Formation and Memory CI recovered after process loss in bounded production tests. ContextDB still runs one instance of each worker, with no high-availability, multi-VM failover, or availability SLO.

Publication rules

What this page will never do

  • Publish uptime percentages before they are measured over a real service period.
  • Claim availability, regions, or recovery objectives that do not exist.
  • Show a green “all systems operational” for components that are still scoped.

Contact

Report an issue

Something broken? Email gaurav@saaslabs.co.