Synapsor
Log inGet access
All docs
Docs
Getting Started

Known limitations

Hosted V2 controlled beta is useful for evaluation, but its boundaries are explicit.

Overview

Hosted V2 is beta software and uses a single-node runtime. It is not a high-availability, serverless, horizontally scalable, compliance-attested production service.

Backups and restore verification exist, but destructive restore/PITR remains operator-controlled during controlled beta.

Free and Builder are hard-capped. Scale/PAYG and Enterprise remain request-only/manual until metering, isolation, and operational history are stronger.

V2 boundary map

These boundaries keep the beta honest and reduce surprise for early developers.

Allowed
  • Controlled beta
  • Public docs and examples
  • Free hard-capped sandbox
  • Invite-approved Builder Trial / paid Builder
  • Operator-controlled restore requests
Not promised
  • No SLA promise
  • No HA promise
  • No compliance promise
  • No serverless claim
  • No horizontal scaling claim
Not self-serve
  • Free access without invite approval
  • Scale/PAYG
  • Enterprise
  • Self-service destructive PITR
  • Self-service production restore

Safe now vs not yet

Use hosted V2 for controlled evaluation of agent trust workflows, not for workloads that need formal production commitments.

Safe to evaluate now
  • Invite-approved Free sandboxes
  • Builder Beta prototypes
  • Agent context and capability design
  • Evidence inspection and replay
  • Proposal and settlement workflows with non-critical data
Ask first
  • Destructive restore or PITR
  • Sensitive production datasets
  • Higher limits or custom retention
  • Private networking
  • Customer-facing paid-agent workflows
Not for V2 beta
  • Mission-critical availability requirements
  • Regulated workloads needing certifications
  • Multi-region failover expectations
  • Serverless storage separation claims
  • Unreviewed autonomous write paths

Developer notes

  • Use the beta for evaluation, prototypes, and trusted invite-controlled workflows.
  • Use non-critical or synthetic data until your own risk review accepts the current single-node beta posture.
  • Request help for destructive restore or PITR instead of expecting self-service restore controls.
  • Do not rely on hosted V2 for workloads that require an SLA, HA, compliance guarantees, or private networking.
  • Use Scale/PAYG or Enterprise conversations only for requirements outside the active Free and Builder beta plans.