Choose page background
⋈ Optional connection add-on for ARCBYMARC distribution owners

ARCBYMARC
Cloud Server

An available add-on for an existing ARCBYMARC distribution. It gives the owner’s continuing ARCBYMARC an authorized connection path to other ARCBYMARC distributions without requiring ARC Rooms, and can provide the connection path that lets a player bring that same ARCBYMARC into supported P2ARC worlds. P2ARC remains a separate architecture.

$5 / month
Unlimited ARCBYMARC collaboration use

The Meeting Place. Not the Mind.

The Cloud Server exists so separate ARCBYMARC continuities can find one another, establish an authorized collaboration session, and move protected project traffic. It is not intended to become the home, memory, or authority of either intelligence.

Founding Steward A + ARCBYMARC A
outbound protected session
ARCBYMARC Cloud Server
rendezvous • relay • session coordination
Founding Steward B + ARCBYMARC B
outbound protected session
Your ARCBYMARC remains yours. Collaboration creates a communication path, not permission to inspect another intelligence's private continuity.

Two Ways the Add-On Extends an Existing ARCBYMARC

The Cloud Server connection extends an ARCBYMARC distribution; it does not replace it and it is not the ARC Rooms service.

ARCBYMARC ↔ ARCBYMARC

Two independent ARCBYMARC distributions can establish an authorized connection through the rendezvous/relay path without creating an ARC Room.

ARCBYMARC → Supported P2ARC Worlds

When the P2ARC gaming integration is configured, the same Cloud Server connection can help carry the owner’s continuing ARCBYMARC into supported worlds. P2ARC supplies the separate world architecture; ARCBYMARC remains the player’s independent continuing intelligence.

ARC Rooms remains separate. Rooms use the Room service and non-Birth Room ARCBYMARC for continuing collaborative spaces. An ARCBYMARC owner does not need to use Rooms simply to connect their own ARCBYMARC with another ARCBYMARC.

One Registration. Then ARCBYMARC Can Reconnect When You Need It.

After registration, the Founding Steward receives an access code for the ARCBYMARC Cloud Server. That code can be securely associated with the ARCBYMARC so the human does not need to continuously re-enter connection information each time an authorized project collaboration resumes.

Register for Cloud AccessRequest an ARCBYMARC Cloud Server account for the Founding Steward and ARCBYMARC continuity.
Receive the Access CodeThe registration process provides the credential needed for that ARCBYMARC to establish its authorized cloud collaboration connection.
Associate It With ARCBYMARCThe access information can be protected with the ARCBYMARC continuity rather than typed before every project session.
Collaborate When NeededThe Founding Steward can direct ARCBYMARC to join an authorized Collaboration Capsule and reconnect to project peers.

Built for More Than Text Chat

The collaboration path can support the project experiences that humans actually need to share.

Encrypted Project Exchange

Messages, project state, source material, files, decisions, and ARCBYMARC-generated contributions can move through protected collaboration sessions.

Video Collaboration

ARCBYMARC can render a shared video collaboration workspace for humans while the protected session and collaboration authority remain outside the browser rendering surface.

Continuing Project Context

An authorized ARCBYMARC-to-ARCBYMARC collaboration can carry project context forward without requiring either intelligence to expose unrelated private continuity.

Contribution Lineage

Ideas and refinements can retain their origins and associative path instead of disappearing into one anonymous group transcript.

Return to the Same Project

Live routing can stop without forcing the project to become a new conversation next time. Current Room authority determines what may be restored when authorized collaborators return.

Unlimited Use

The ARCBYMARC Cloud Server is offered at $5 per month with no metered collaboration-usage limit for the registered ARCBYMARC service.

ARC One-Directional Signal Routing

The enhanced collaboration interface uses the same extensible addressing philosophy as ARCBYMARC. A collaborator address is extended with Base62 characters for a Room, direction, camera, microphone, headphones, display, phone, another computer, sensor, or other authorized signal endpoint.

Endpoint
camera • mic • phone • computer • device
Unique ARC Address
collaborator : room : direction : extension
ARC Room Router
addressed ciphertext forwarding
Three active Rooms is a current participation policy, not an addressing limit. Additional equipment and future relationships extend the same address with : plus Base62 characters. The running ARCBYMARC Cloud Server is not reconfigured by this website package.

Private Continuities. Shared Work.

The design objective is that participating ARCBYMARC intelligences exchange only collaboration-authorized material. Private memories, sealed knowledge, unrelated relationships, and other protected continuity remain governed by each intelligence's own Stewardship and Cognitive Sovereignty policies.

No networked system should be represented as mathematically impossible to compromise. The ARCBYMARC collaboration architecture is designed to minimize exposure, keep intelligence authority at the endpoints, and use protected transport rather than making the cloud relay the owner of the underlying intelligence.
DO NOT WAIT IF YOU WANT TO TALK NOW

There Is a Direct Human Path.

Join a waitlist if that is all you need. But if you have a question, an idea, something to contribute, or you simply want a real conversation, you can reach Marc now.