Relay is the flagship entry gateway for optional governed connections within IMMA. You can start the free personal workspace before connecting a Relay. Hosted Relay access remains in development and requires approval for your account. Relay is being built to recognize a project, apply its permissions, route work to an approved destination, and return its real result.
Relay service access remains in development. Joining its waitlist does not create an IMMA account, activate billing, or grant Bridge access. Personal workspace account setup is separate.
RELAY MISSIONCONNECTION VALIDATION
YOU ASKInspect the approved project and return a verified result.
PROJECTRecognized→POLICYGoverned→ROUTEApproved
IMMA BRIDGEAllowlisted boundary
VALIDATING
OPTIONAL RELAY ROADMAP · FREE WORKSPACE SIGN-IN IS SEPARATE
Start with the existing IMMA sign-in. A free personal workspace does not require IMMA Pro or community membership. This public guide is not a live connection monitor.
01
Our Relay service
Use our Relay only when it is available and approved for your account and workspace. Public customer availability and automatic setup are not yet verified.
Next: sign in to inspect your account-scoped connection state and its next action. A configured address or badge alone does not prove an executor is ready.
Compatibility and an authorized connection must be checked before your instance can power the workspace. Automated public enrollment and a verified one-click installer are not available here.
Next: confirm the supported setup instructions, instance ownership, allowed capabilities and provider limits with your operator. Use only addresses and access instructions supplied for your account.
Check before you run. In the signed-in workspace, verify the connection and permitted capability, review any required human approval, and confirm a real result returns to its originating Work or conversation. If the service is unavailable, keep the saved request and follow the displayed recovery step. Do not paste credentials into this website.
Existing usage and provider policies apply. Free workspace access is not unlimited AI, compute, hosting or paid services.
FLAGSHIP SYSTEM // IMMA OS
The connective tissue behind the work.
Relay is the reason the IMMA system can turn a normal-language request into a governed, traceable path across projects, agents, services, and approved destinations.
01 / CONNECTOne signal, many surfaces.02 / DIRECTContext becomes action.03 / RETURNEvery result comes home.
ONE CLEAR LOOP
Ask once. Keep the work connected.
The experience is being designed for normal language first. Technical routing stays behind a governed, inspectable process.
01ASK
Describe the outcome.
02GOVERN
Apply identity, policy, and approval.
03ROUTE
Select an eligible destination.
04RETURN
Bring back the trace and result.
CURRENT PRODUCT DIRECTION
Less coordination. More completed work.
These capabilities are grounded in the current Relay MVP. Public availability remains in development.
01
Project recognition
Relay is being built to identify which approved project a request belongs to before work moves.
02
Approved destination routing
Project associations and permissions guide where a mission may go. Unclear routes stop for review.
03
Compact context packages
The intended pattern moves the mission, constraints, and relevant context—not an uncontrolled history dump.
04
Model-tier decisions
Routine, implementation, and higher-risk work can be assigned different reasoning tiers with escalation when needed.
05
Mission history
The route, decision, status, trace identifiers, and result are designed to stay connected to the project.
06
Private Bridge boundary
Authorized work crosses a governed boundary through allowlisted tasks, verified correlation, and truthful availability states.
THE BRIDGE // CONNECTION VALIDATION
The boundary is built to verify before it trusts.
IMMA Bridge is the governed communication and execution boundary between Relay and an authorized Node or tool. The current implementation is intentionally narrow: one preapproved, non-mutating repository inspection path with fixed identity, task allowlisting, private transport configuration, and response correlation.
Truthful by design. If the private Bridge or node is unavailable, Relay returns an unavailable state instead of pretending the mission ran.
BRIDGE READINESSPRE-PRODUCTION
Relay mission foundationBUILT IN MVP
Bridge request and result contractIMPLEMENTED
Allowlisted read-only inspection pathIMPLEMENTED
Private node receiver pathPREPARED
Live end-to-end node connectionVALIDATION PENDING
General-purpose remote executionNOT AVAILABLE
GATE 01 // COMING SOON
Connect when you're ready. Keep your work in IMMA.
Join the list for Relay product updates, connection milestones, and future early-access invitations. Your personal IMMA account does not depend on this waitlist.