Vyral contract core connecting stable application contracts to interchangeable infrastructure
Provider-portable application substrate

Vyral — own the contract layer

Keep records, retrieval, durable execution, and agent-facing work behind stable contracts. Change infrastructure without teaching your product a new language.

Read the docs →Explore the architecture

Pre-1.0 Local paths are usable. Provider maturity is evidence-scoped.

129cataloged operations
281public schemas
5runtime adapters tracked
2026-07-28stateless MCP profile
The contract plane

Infrastructure should be a choice,
not a constraint.

Vyral gives application code a stable capability model. Adapters absorb provider shapes; versioned contracts, conformance suites, and qualification evidence make their behavior inspectable.

your applicationstable consumer surface
contract plane
localcloudmodelsworkers
Application-owned semantics

One vocabulary above the provider layer.

Portable envelopes and explicit invariants keep vendor SDKs at the edges of the system.

Honest portability

Qualification is a claim boundary.

An adapter’s maturity is recorded with evidence; presence in the tree is not a production claim. Immutable retrieval generations can also prove exact identity and complete logical coverage.

Local-first mechanics

Build the real workflow before the cloud bill.

Local storage, retrieval, execution, and deterministic providers exercise the same consumer contracts.

See the boundary

Change the deployment.
Keep the request.

Select a capability and deployment path. The provider changes beneath the contract; operation identity, completion semantics, and the consumer-facing shape stay put.

Consumer requestPOST /collections/{collection}/records{ "id": "order-42", "partitionKey": "tenant-a" }operation · upsertRecord
stable contractunchanged
Deployment choice
Portable result200 · mutation committedatomic completion

Selected: Local · SQLiteReference path

Deployment selection does not imply equal maturity. Qualification remains an explicit, source-derived claim for every adapter.

A coherent substrate

Move the seams to where
they can be governed.

Records & objects

Partitioned records, metadata, vectors, immutable payloads, manifests, etags, and snapshots—without making a storage vendor your application model.

SQLitePostgresFirestoreDynamoDB

Retrieval & RAG

Source-native, lexical, vector, and hybrid retrieval with deterministic ingestion, bounded context, citations, diagnostics, profiles, and evaluation receipts.

hybridcitationsGraphRAGevaluation

Durable execution

Idempotent admission, receipts, retries, cancellation, waits, checkpoints, artifacts, leases, plugins, and external workers under one lifecycle contract.

receiptsretriesworkersplugins

Provider & agent work

Normalize model discovery and AI runs, then expose selected capabilities through stateless, gateway-friendly MCP without surrendering the run authority.

AI runsMCPpolicytelemetry
A real acceptance boundary

Accepted means
recoverable.

Long-running mutations return only after work is durably admitted. The receipt preserves one resource identity across polling, process restart, and a safe replay of the original request.

Read the admission contract →
admission trace
POST/execution/runsIdempotency-Key: order-42:capture
HTTP 202 · durable boundary established
version
vyral.admission.v1
admissionId
adm_83f2…a91c
resourceId
run_7f2a
statusUri
/execution/runs/run_7f2a
replayed
false
  1. 1
    admittedstored before response
  2. 2
    queuedsafe across restart
  3. 3
    runninglease + heartbeat
  4. 4
    resultsame polling URI

The response is returned only after the run can be recovered independently of this request.

MCP 2026-07-28

Self-describing requests.
Ordinary infrastructure.

Vyral’s preview MCP surface is stateless and REST-backed. Version, route, capability, and authorization context travel with every request, allowing gateways to make decisions before any call reaches any healthy instance.

  • ✓ No sticky session requirement
  • ✓ Header-based routing and policy context
  • ✓ Durable work returns task envelopes
  • ✓ Write tools remain explicit opt-ins
Read the stateless MCP design →
POST /mcp
mcp-version: 2026-07-28vyral-route: retrievalauthorization: Bearer ••••••vyral-capability: searchRecords
route + authorize→
plain gatewaypolicy at the edge
instance 01instance 02instance 03
Proof, not adjectives

Readiness is recorded,
not implied.

Claims must be supported by evidence. This snapshot reports 1 locally conformant, 1 prototype, and 3 live-qualified execution adapters.

AdapterLevelEvidence
AWS DynamoDB and SQS execution runtimeLive Qualified6 records
Azure Durable Functions execution runtimeLive Qualified5 records
Google Firestore and Cloud Tasks execution runtimeLive Qualified6 records
Local SQLite execution runtimeLocal Conformant3 records
Temporal execution runtimePrototype1 record
Snapshot 4443830Inspect qualification evidence →
Start on your machine

Exercise the contract
before choosing the provider.

The default server uses local SQLite records and traces plus filesystem object storage. Run the Python or JavaScript example against the same HTTP surface.

Open the quick start
vyral — local
$ scripts/start-local-server.sh

# in another terminal
$ curl http://127.0.0.1:5220/readiness
{"status":"ready"}

$ python3 examples/python/rag_quickstart.py
collection ready · 3 documents · citations preserved
Stable contracts. Replaceable providers.

Make the application
the durable part.

View source on GitHub ↗