Documentation and setup guides

Sign in and choose a workspace

Use the email address attached to your OwnServa account. Check its spelling and domain if sign-in reports invalid credentials. Password sign-in requires a verified email address; authenticator protection, when enabled, adds a second step.
Choose your workspace from the dashboard selector. Resources belong to that workspace, so select the correct one before connecting a server, deploying an application or inviting a teammate.
If public registration or an email-dependent action is unavailable, contact support. The operator must finish policy publication and email-delivery setup before those features are ready.

As a workspace owner or admin, open My Servers → Connect server, name the server and generate a private connection link. It is single-use and expires after ten minutes. Opening the link prepares the matching installer without sending its credential in the page URL request.
Copy the Ubuntu install command from the connection dialog or private link. Paste it into the Ubuntu server's SSH terminal. It detects amd64/arm64, downloads the published agent, checks the pinned SHA-256 values, uses this installation's API address, pairs the server and enables its service. No separate checksum lookup or token entry is required.
Use Ubuntu 22.04, 24.04 or 26.04 LTS with systemd and curl, and administrator privileges. Docker inventory and managed-container controls require an explicit checkbox and an existing Docker installation. Application deployment has additional prerequisites. The command contains a short-lived private credential and can remain in terminal history; keep it private and remove it from history after use. Existing OwnServa identities are preserved rather than overwritten.
Return to My Servers and wait for the first confirmed heartbeat. Pairing alone does not mean the server is online. If it remains offline, check its outbound HTTPS connectivity and the ownserva-agent systemd service logs.

Open Applications or Deploy New App and choose a connected, ready server. Use a supported container image or GitHub repository with a Dockerfile. Configure the application port, health path and runtime variables before deploying.
For a private GitHub source, configure the application's dedicated repository credential. Sign-in with GitHub does not grant repository deployment access. Keep access tokens out of public issues, build output and client-side variables.
Review the deployment's status and logs. A release must pass its health checks before promotion; an uncertain or failed deployment is not confirmation of success. Use release history to select a supported rollback when necessary.
Automatic GitHub deployments require a configured signed webhook and the applicable workspace entitlement. Templates and AI models also need operator-approved images and sufficient server resources; a listed recipe is not an already running service.

Use Networking & Tunnels to request a public route for a ready application. Public exposure requires your confirmation and an operator-provisioned gateway. A route is usable only after DNS, HTTPS and the current application release are verified.
Use Domains to connect an existing domain and complete its ownership proof. Use DNS Management for supported records on a zone managed by the configured authoritative provider. Review record names, targets and TTLs before saving changes.
Registrar purchases, transfers and renewals require enabled provider credentials, registrant details and verified payment. A quote or pending order is not proof of domain ownership. Gateway and registrar integrations are not currently configured on this installation.

Owners and admins manage Team Members within their permitted role boundaries. Share invitation tokens privately with the intended recipient. The recipient needs the matching verified email address; invitations expire after seven days.
Open Account Settings to edit your profile, manage sessions, connect or disconnect supported sign-in providers, change credentials, or request an account export. Sensitive actions require a fresh email proof; email delivery must be configured first.
Enable authenticator protection when available and save recovery codes somewhere secure outside the account. Password reset does not remove an existing authenticator requirement. Never post a password, pairing token, recovery code or private key in a support issue.

Monitoring shows reports received from connected agents. Missing or stale measurements are not zero usage, and GPU discovery alone does not establish driver or model compatibility. Billable bandwidth accounting is not available.
Backups require an approved destination, encryption credentials and supported application volumes. A cold backup can stop the application temporarily and needs explicit consent. Check completion and the application's health after restart.
Scheduled cold backups require a successful prior backup and readiness checks. Recovery creates an isolated volume for inspection; it does not automatically activate restored data. Keep independent backups and test the entire recovery process.

Billing & Subscriptions shows configured prices and available payment methods. Live payments are currently disabled. When enabled, check the total price, currency, tax information and renewal interval before separately accepting recurring billing.
Use the cancellation control to stop future renewal and confirm the resulting status. A refund or statutory withdrawal request is a separate process; the public withdrawal form works without signing in and does not require a reason.
Use the public data-rights form for access, correction, erasure, restriction, objection, opt-out or an appeal. Keep its timestamped receipt. A submitted request is recorded for operator review; it does not automatically disclose data, cancel a contract or issue a refund.

The control plane is hosted at ownserva.com with HTTPS. Account and workspace management are deployed. Customer agents, gateways, merchant accounts, registrar access and external backup destinations must be configured and tested before their dependent services can be used.
Platform administrators use Account Settings to complete and publish reviewed legal information and manage the data-rights queue. Draft terms are a starting point; the remaining privacy, retention, transfer, provider, refund and tax arrangements need operator review.
Configure SMTP and test real delivery before relying on registration verification, password reset or security proofs. Platform Admin contains registered users, consented visit statistics, the contact inbox, Google/GitHub sign-in settings and policy publication. Preserve the database and encryption keys before infrastructure upgrades. The current migration chain ends at 017.
Buildpacks, ZIP/Compose imports, automatic restored-volume activation, GeoDNS, app replication and general bandwidth billing are not available. A source implementation of an integration does not mean its provider has been enabled or accepted for production.