Skip to main content
Solia Direct

Platform / Sandbox & Production

Evaluate safely. Activate Production deliberately.

Sandbox and Production are separate, persistent environments. Laboratory Sandbox supports self-service onboarding and configuration; Program-backed Partner API Sandbox access follows an approved lab-backed Program and grant.

What it enables

A safe path from evaluation to governed operation.

Laboratories can configure Programs and exercise synthetic workflows without touching Production. Authorized partners can test after a Program-backed grant is approved. Production is not a switch: readiness is fail-closed and evidence-driven, and activation requires technical, operational and commercial approval.

  • Persistent Sandbox after go-live
  • Synthetic people, orders and results
  • Environment-bound API credentials
  • Isolated Programs and adapter configuration
  • Partner integration and webhook testing
  • Mapping and lifecycle validation
  • Post-live rehearsal and regression testing
  • Evidence-driven Production readiness

System boundary

Synthetic Sandbox testing does not prove external LIS compatibility or authorize Production.

Production uses separate environment-specific Programs, credentials, adapters and mappings. Real-interface validation and technical, operational and commercial readiness are required before controlled approval; synthetic testing alone never proves external LIS compatibility.

Separated by design

Sandbox credentials and synthetic data cannot operate against Production resources.

Persistent test space

Sandbox remains useful after launch for partner certification, rehearsals and regression checks.

Fail-closed readiness

Missing evidence, unresolved mappings or incomplete controls block Production activation.

Controlled activation

Go-live requires technical sign-off, operating readiness and commercial approval.

Product proof

Sandbox is persistent and synthetic. Production remains separate, evidence-driven, and explicitly approved.