Menu

Product hub

Controlled BetaAlphaFutureVerification Required

Concordia

Concordia documentation presents the product family honestly: local Cache and Time Series behavior first, Gateway alpha routes and Storage validation boundaries clearly labeled, active compatibility evidence separated from shipped contracts, and Edge Workflows kept future-facing until runtime support exists.

Current availability

Private Beta. Public beta is scheduled for .

Primary Evaluation Path

  1. Start local CacheUse the smoke path for health, auth rejection, key operations, and persistence checks.
  2. Inspect alpha routesKeep Gateway and Time Series behavior tied to local diagnostics and alpha write evidence.
  3. Check validation gatesSeparate ready, design-ready, planned, local-only, and diagnostic evidence before publishing claims.
  4. Track future directionHold Edge Workflows and broader deployment posture for later runtime-backed docs.

Surface Status

Product-family foundation

Alpha

Frame Concordia as a Rust product family organized around Cache, Time Series, and Edge Workflows on a shared platform foundation; do not present every component as equally mature.

Evidence: Fact sheet: README.md and PRODUCT_OVERVIEW.md

Local Cache validation

Alpha

Use the local smoke path for cache health, missing-authorization rejection, key write/read, count, placement diagnostics, and binary persistence across restart.

Evidence: Fact sheet: LOCAL_RUNBOOK.md

Gateway alpha route

Alpha

Describe diagnostics and protected local alpha write behavior, while keeping JWT enforcement, owner forwarding, quorum responses, and cross-node replication out of current claims.

Evidence: Fact sheet: README.md

Time Series local model

Alpha

Keep TSDB wording tied to local model, append/query, retention, and routing-diagnostic primitives until durable storage, authorization, and replication evidence land.

Evidence: Fact sheet: README.md

Storage validation and active compatibility

Alpha

Show storage and compatibility work as validation-bound alpha surfaces, with local-only, in-memory, diagnostic, design-ready, and planned gates kept visibly labeled.

Evidence: Fact sheet: README.md and ALPHA_VALIDATION_MATRIX.md

Edge Workflows direction

Future

Treat workflow actions, Time Series input, and edge direction as future-facing until runtime support and product approval exist.

Evidence: Fact sheet: PRODUCT_OVERVIEW.md

Route Families

Cache

Local Cache smoke behavior, protected route expectations, key operations, counts, placement diagnostics, and persistence checks.

Gateway

Diagnostics and protected local alpha write behavior, with quorum, process-owner forwarding, and cross-node claims held back.

Storage validation

Validation shells, WAL-boundary work, metadata fixture evidence, rollback gates, and release artifact proof before broader claims.

Time Series

Local TSDB append/query, retention, routing diagnostics, and model behavior before durable distributed maturity.

Active compatibility

Compatibility service behavior and protocol fixtures that prove bounded checks without turning fixtures into shipped contracts.

Edge Workflows

Future product direction for Time Series input and workflow actions, held out of current user workflows until runtime support exists.

Boundaries to Keep Visible

Uneven Maturity

Cache, Gateway, Storage, Time Series, active compatibility, and Edge Workflows should not be described as having the same readiness.

Local Evidence

Local smoke or diagnostic results can support first-success docs, but they do not prove distributed deployment behavior.

Gateway and Auth

Gateway alpha copy must keep JWT enforcement, process-owner forwarding, quorum responses, and cross-node replication out of current promises.

Future Workflows

Edge Workflows stay as future direction until implementation, workflow semantics, idempotency, and side-effect boundaries are reviewed.

Safe Next Steps

  • Available now

    Run the Cache quickstart

    Exercise local Cache put, get, count, TTL or stale-version behavior, and persistence limits.

  • Available now

    Review Concordia evidence

    Use the evidence index before strengthening Cache, Gateway, Time Series, Storage, active compatibility, or workflow claims.

  • Available now

    Try TSDB and Gateway alpha tutorial

    Append local Time Series samples, query recent values, then inspect Gateway readiness and alpha write boundaries.

  • Available: DOCS-061

    Use local curl examples

    Reuse bounded curl examples for Cache, TSDB, Gateway alpha readiness, and active compatibility diagnostics.

  • Available now

    Read runtime surface reference

    Separate Cache HTTP, Gateway alpha, Storage validation, active service, and protocol fixture surfaces.

  • Available: DOCS-041

    Map runtime boundaries

    Classify Cache, Gateway, Storage, TSDB, active compatibility, fixtures, and Edge Workflows as alpha, future, or verification-required.

  • Available: DOCS-042

    Read known limits

    See what happens for local bearer tokens, Gateway diagnostic writes, Storage validation flags, future frames, and Edge Workflows.

  • Available: DOCS-053

    Use validation runbooks

    Check what Cache, Gateway, Storage, TSDB, active service, protocol fixture, and validation script output proves and does not prove.