Getting started on Cloud

Register at captivo.io/register. One Captivo account covers both products; the Access free tier is attached to the account the moment it is created, so there is no separate sign-up and nobody has to approve anything.

If your organisation already has a Captivo account, sign in with it rather than creating a second one: the Access console belongs to the organisation, not to the person who clicked first.

From the Captivo dashboard, open Captivo Access. You are asked to name your workspace once; that name becomes your console address, <your-org>.cloud.captivo.io. Pick a short, stable name: it is also the middle part of every vendor address you will publish.

Each resource you publish later gets an address of the form <label>.<your-org>.cloud.captivo.io; you type only the label, the rest is appended for you and its certificate is issued automatically. A web app can also be published on a domain you own (your own portal.example.com): point an A record at the address the console shows, press Verify, and the certificate follows.

The first time you open the console you register a passkey: Touch ID, Windows Hello, or a hardware security key. There are no passwords anywhere in Captivo Access, for admins or for vendors. The account you create here holds the Admin role; everyone else arrives later by invitation.

The Connector is the only piece that lives on your side. Under Infrastructure → Connectors, add a connector and copy the one-line command the console shows; run it on any Docker host inside your network that can reach the apps you want to publish. It dials out to connect.cloud.captivo.io and to your console over port 443, and never listens for an inbound connection, so your firewall gets no new rule.

The command starts the connector together with the two session engines it needs for remote desktops and the isolated browser, so there is nothing further to enable. Within a few seconds the console lists it as Online. Every detail, including the egress boundary and the backup you owe the recordings, is in Installing the Connector.

Under Infrastructure → Resources, add the internal app or server: a label for its public address, the internal address the Connector should reach (for example http://10.0.5.20:8080), the connector that reaches it, and the access method: web app, remote desktop (RDP/SSH/VNC) or isolated browser. See Defining resources.

Then invite the vendor under People → Invites and grant them that resource under Access, with a start and end if the work is time-limited. The vendor opens the invitation, registers a passkey, and reaches only what they were granted. The full flow, including approvals and weekly schedules, is in Inviting a vendor and granting access.