Presence programs
Reality Relay Platform
Workspace
Next best action
Build the first valuable presence.
Start with a project, then register the scene and Space that will create the proof.
Versioned packages
Physical endpoints
Prepared sessions
Presence pipeline
From intent to physical proof.
- 01ProjectDefine the valuable presence.Start
- 02Source assetPreserve the original with ownership and provenance.Waiting
- 03Presence ScenePackage content, behavior and grounding rules.Waiting
- 04Relay hardwareRegister the endpoint and calibration profile.Waiting
- 05Session runbookCheck compatibility before physical launch.Waiting
Runtime truth
Hosted core ready.
Pair the first Space.
The signed control loop is implemented. Physical controls remain locked until a real endpoint is paired, reporting fresh health and calibrated with evidence.
- Prepare / play / switch / stop
- Signed Runtime
- Remote device control
- Awaiting first pair
- Physical proof
- Human-reviewed gate
01
Create the container for a real pilot.
Name the result you want to prove—not the device you want to show.
Private asset library
Keep every original durable, private and traceable.
Source registry
Media before transformation.
Uploads are stored privately. New assets remain unverified until a trusted media worker checks their checksum, format and physical-presence requirements.
02
No durable source asset yet.
Upload an image, video or 3D model into a project. The original is preserved before generation, repair or display adaptation begins.
Start here
Create a Scene without learning the system first.
Begin with an idea, image, video or 3D model. Presence Studio guides you from source to display-ready content.
- 1Choose a projectKeep related content and hardware together.Next
- 2Create the SceneStart from text, an image, video or a 3D model.Waiting
- 3Check it for displayConfirm format, grounding and readiness for a Space.Waiting
Your Scenes
Continue creating or check what is ready.
Each Scene keeps its content, versions and display checks together. Technical details stay available when you need them.
YOUR FIRST SCENE
Nothing here yet. Start with what you already have.
Presence Studio will ask whether you want to use text, an image, a video or a 3D model, then show only the tools you need.
Creator publishing
Move finished work into the Community.
Originals stay private. Only the moderated release becomes discoverable, and downloads remain license-controlled.
Your releases
Submission status.
R
No Community submission yet.
Upload and verify a source asset, then return here to submit the release.
Relay Hardware
Physical endpoints with known capabilities and calibration.
Endpoint inventory
Calibration is part of the product.
A Space is not “ready” because a screen turns on. Connection, resolution, capability and physical proof remain separate gates.
03
No Space registered.
Add the current portrait HLD or a preview endpoint. Every Space starts unpaired and uncalibrated by design.
Session orchestration
Prepare before you press play.
Operator console
No paired Space
Prepare, play, pause, recover and stop unlock only when an approved scene meets a verified, connected Space.
Cloud safety boundary. Hosted stop commands depend on endpoint polling. For an immediate local physical stop, terminate the companion on the Space; it performs a local emergency stop before restart.
Runbooks
Compatibility before claims.
A runbook joins one scene to one Space and records every missing gate. Creating one does not imply the hardware has launched.
04
No session runbook.
Register a scene and Space in the same project, then test whether their declared capabilities match.
Organization access
One operating team. Explicit authority.
Members
Your organization
Owners and administrators control invitations. Every permission is enforced in the database.
Pending access
Invitations
Links expire, can be revoked, work once and must be opened by the invited email.
Access activity
Recent control changes
Append-only organization events recorded by the database.
Free platform · metered creation
Build for free.
Use credits when AI creates.
Starter
1,000 credits
A straightforward first top-up for generating and adapting spatial content.
- One-time purchase
- Shared organization balance
- Exact cost shown before generation
Most useful
2,500 credits
More room to generate, compare and refine several presence-ready directions.
- No subscription
- No expiration in the current beta
- Credits added after verified payment
Builder
5,000 credits
A larger balance for teams iterating across multiple scenes and use cases.
- One-time purchase
- Organization-wide balance
- Full immutable usage history
Purchases are subject to the Reality Relay Terms. Hardware pilots and custom deployment work are scoped separately.
What uses credits
Pay for creation, not access.
AI video generation, conversion and enhancement use credits. Uploading, organizing, playback and device management stay free.
Credit activity
Purchases and usage
Account security
Sign-in and recovery
- —
- Providers
- —
- Status
- —
- Last sign-in
- —
The reset link expires and can only be used once. Other sessions are revoked after the password is changed.