Can a solo developer use Isolation without a team?

Yes. Every account works inside an organization, and a solo developer is an organization of one. You are its Owner, you connect your own servers for free, and nobody else ever needs to be invited.

Who can stop a session that is not theirs?

An Owner or Admin can list and stop any session on the organization's servers. Nobody can open a session that is not theirs, whatever their role.

Organizations, roles and invites

Q: How long does an invitation last?

Fourteen days. Inviting the same address again replaces the pending invitation with a fresh link and a fresh expiry.

An organization is the tenant. Owners handle billing and deletion, Admins run servers and invites, Members launch. Invite by email, change roles, leave.

Organization roles and invites work like this: an organization is the tenant, every server and the prepaid balance belong to it, and every person in it is a member with one of three roles. An Owner handles billing, the plan and deleting the organization. An Admin manages servers and invitations and can stop any session on the organization's servers. A Member launches sessions of their own workspaces on those servers. A solo developer is an organization of one, and is its Owner.

Nothing is created behind your back. Your first organization is the one you name during onboarding, when you create an organization and connect a server. Companies then invite people into theirs.

What each role can do

	Member	Admin	Owner
Launch, save, stop your own sessions	yes	yes	yes
Open a session	only your own	only your own	only your own
List and stop any session on the organization's servers		yes	yes
Add, remove and pick the default server		yes	yes
Invite people, withdraw invitations, remove non-owners		yes	yes
Add funds to the balance		yes	yes
Read the activity log		yes	yes
Change anyone's role, invite or remove an Owner			yes
The plan, and deleting the organization			yes

Workspaces and sessions stay the member's at every role. A teammate's workspace is not in your list, and their session does not open for you. What an Owner or Admin gets is the ops right: whoever pays for a metered Cloud Server can stop a session that somebody forgot. How that plays out for shared previews is on yours by default, and sharing a web preview.

How do I invite someone?

An Admin or Owner invites an email address, from the Team page, from a chat app, from an MCP client or from the CLI. The invitee gets a link by email. The link works once, is tied to that address (they sign in with it to accept), and expires after 14 days. Inviting the same address again replaces the pending invitation with a fresh link. Withdrawing an invitation kills its link on the spot.

/members                         who is in the organization, and who is still invited
/invite ana@example.com          invite as a member
/invite ana@example.com as admin invite as an admin

An Admin can invite up to Admin. Only an Owner can invite somebody as Owner. A new membership arrives with the starter agent, Isla, already on the member's roster.

Changing roles, removing people, leaving

Only an Owner changes roles, including handing ownership to somebody else. An Admin or Owner removes a Member or Admin; only an Owner removes another Owner. When someone is removed, their access ends immediately: the tokens their sessions used to reach the organization are revoked on the way out. Their sessions keep running until somebody stops them, which an Admin can do from the Team page or with /stop.

Anyone can leave an organization themselves. Leaving is the member's own act, so no role is needed for it. On the website you land in your next organization, or on onboarding if you have none left.

The last-owner rule. An organization always keeps at least one Owner. Demoting the last Owner, removing them, or letting them leave is refused with a plain message: make somebody else an Owner first, or delete the organization.

Deleting is the Owner's alone, and it refuses while the organization still has Cloud Servers, open sessions, or a balance of a cent or more. Real value is settled deliberately, never destroyed as a side effect. Connected Servers are released with the organization.

The organization switcher

You can belong to several organizations, each with its own name, URL slug, avatar color and default launch server. The switcher at the top of the sidebar moves you between them; every page is at /<slug>/<page>, so a link a teammate sends you opens in the right organization. The active organization is the one every request is scoped to. If you are removed from the one you were looking at, the website falls back to your oldest membership rather than showing a dead page.

Personal and Professional

A personal organization is on Personal, which is free: one member, unlimited Connected Servers, the whole web surface including the cost view, your own AI credentials, ssh into every session, and Cloud sessions paid by the second from prepaid credits — one Cloud-sessions server per organization. Professional is $20 a month flat (or yearly at a discount) for up to five members and unlocks the team: invitations, roles and shared servers, ssh into Cloud sessions from IPv4-only networks through Isolation's doorstep (every plan has direct ssh over IPv6) and private connectivity for Connected Servers. Enterprise is $100 a month plus $2 per member from the first one, with no member cap, and every paid month credits $20 of compute balance. Usage stays metered on top of the plan and draws from the organization's balance — topped up by hand or automatically under a threshold you set — as described in Cloud Servers and billing. An owner picks the plan and the billing interval on the plan page (Stats → Plan); an upgrade applies at once, prorated, and a downgrade at the end of what was paid for. The invitation that would make a Personal organization two people, or a Professional one six, is refused with the reason. Every invitation, role change and removal is recorded in the activity log, with who did it and from where.