Connector
Enable hosted capacity from a self-hosted control plane.
A Connector authorizes a self-hosted Infra installation to manage selected Solarius-hosted resources. It is optional for local fleet, storage, networking, and automation features.
For information exchange between Solarius products, see the Connector documentation. The hosted-capacity grant described here is separate from an Infra–Guard product connection.
Boundary
The Connector exchanges hosted resource configuration, operation references, and observations with the hosted service. It does not create a route between a local private network and a hosted private network, and it does not copy local volume data unless an explicit transfer workflow requests it.
Connector delegation defines the intersection of local permissions and hosted grants. Hosted region access and billing belong to the linked hosted organization. Local organization permissions still control which self-hosted users can request those resources through the Connector.
Prerequisites
- A running, initialized self-hosted installation.
- An organization authorized for hosted Infra capacity.
- Outbound HTTPS to the endpoint shown in the Connector setup flow.
- Synchronized time and a trusted certificate chain.
- Approved hosted regions and residency policy.
No public inbound listener is required solely for Connector enrollment. Network services you expose in hosted regions have their own ingress configuration.
Use the Solarius Compute Cloud reference to identify regional compute hostnames and inspect DNS resolution. Configure Connector access using the service endpoint supplied by its setup flow.
Connect
- Open Installation settings → Connectors → Add Connector.
- Sign in to the hosted organization with Connector administration permission.
- Review the local installation identity and requested hosted scopes.
- Select allowed regions and capacity classes.
- Complete the one-time authorization exchange.
- Verify Connected and refresh the hosted-region inventory.
The authorization credential is stored as protected installation state. A browser session used during setup is not the long-lived Connector credential. Do not export the credential into node enrollment files.
Resource requests
Select a published hosted region when creating a droplet or supported network resource. The local operation links to the hosted operation. The details show which service is reconciling the request.
Hosted images, sizes, quotas, and storage policies can differ from owned regions. A local image ID cannot be assumed to exist in a hosted region. Copy or import an approved image through the supported regional workflow.
Disconnection
A disconnected Connector prevents new hosted changes and delays hosted observations through that path. It does not request shutdown of hosted droplets or stop local agents. Hosted resource charges can continue.
Pending requests remain reconciling until the control plane can determine their hosted outcome. Reconnect and inspect the existing operation before resubmitting with a new idempotency key.
Rotation and removal
Rotate authorization through Connector → Rotate credentials, verify a hosted read and permitted test operation, then revoke the prior credential. Review organization linkage when ownership changes.
Removal is blocked while managed hosted resources or operations require the Connector. Decommission or explicitly transfer those resources first. Removing a local Connector record is not a substitute for deleting hosted resources or settling their retained usage.