ServerSpace
Coordinate host-side execution, mesh connections and runtime routing.
Published host runtime • managed deployment by arrangement
What you can accomplish
Run a configured ServerSpace supervisor on an admitted host, then inspect its actual reported state.
What you bring
A Linux host with Node.js 20+ and Python 3 for the public runtime package. For a managed service, also define the workload, network destinations, persistent state, operator and recovery requirements.
Work through the task
- Choose self-hosted package inspection or an agreed managed deployment. Downloading the package does not assign a customer server.
- Review configuration and dependencies on your host before starting anything. Supply credentials only through your approved host configuration, never on this page.
- Check the host publication and worker state, then verify a bounded workload against its returned result. A fresh lease and ready worker show readiness, not completed work.
What you leave with
The public runtime package supports supervisor/substrate/gateway processes and host publications. A workload needs its own admitted execution path and result; no work is started by viewing this guide.
Where your work stays
A running host can retain process state for its process lifetime. Service files need an agreed durable mount and recovery procedure. Saved JavaScript memory, cross-host migration and crash recovery are not implied by a ready worker.
If something fails
An expired lease or unavailable availability API leaves current host state unknown. Check the host and its logs before retrying work, and reconcile an existing request identity before repeating an external effect.
Available access
A public supervisor runtime package is available. Registered fleet publications are observable on the service page. They do not grant customer provisioning, active mining, an accepted share or a full Bitcoin Core node.
Technical background, package access and updates
Purpose
ServerSpace is the execution and coordination service. Its source exposes owner-gated HTTP interfaces and separate mesh, hardware-abstraction and mining-protocol connections.
Working path
Approved workload → admitted host process → runtime routing or mesh channel → execution result and readback. Service-local worker files and mesh state require durable storage.
Deployment boundary
A published ServerSpace supervisor package and registered host publications are available. The source archive describes additional interfaces that require their own admission and verification. A fresh lease or ready worker does not prove that your workload executed or provision a customer host.
Some source components have network effects at startup. Activation requires a reviewed deployment and owner authority. Recovery and crash consistency remain to be qualified.