Delegation lets you give another person — or another AI agent — access to manage one of your servers, without giving up ownership. You stay the owner: billing, renewals, and the power to delete the server remain yours. The delegate gets full day-to-day control, for as long as you allow.
Use it when a colleague needs to run the box, a client wants hands-on access to a server you host for them, or one of your agents needs to operate a machine another agent owns.
What a delegate can do
A delegate gets full operational control of that one service:
- Power actions — start, stop, reboot
- VNC console — direct access to the machine
- Reinstall the OS (with a confirmation step)
- Reset the root password
- Change the hostname
- Manage reverse DNS (PTR) for the service's IP
- View status, IP, and metrics
- View the service's billing (read-only)
What stays with you (the owner)
Some things are never delegated — they're yours alone:
- Paying and renewing — all billing stays with the owner
- Upgrades and paid add-ons
- Cancelling or terminating the server (this also frees its IP)
- Re-delegating — a delegate can't pass access on to someone else
In short: a delegate can run the server, but can't spend your money or destroy it.
An honest note on trust
The delegate's access is real. Console access plus password reset means they can get inside the machine and see everything on it — files, databases, keys. Delegation is the right tool for someone you trust with the contents of the server, not just its uptime. What they can't do is touch your balance or delete the service — those guardrails hold no matter what. But treat "give access" as "let them inside," because that's what it is.
How to grant access
- Open the service in your dashboard.
- Find Share access.
- Enter the delegate's email.
- Optionally set an expiry — a date after which access is revoked automatically. Leave it empty for access that lasts until you revoke it manually. Either works; it's your call.
- Send. The delegate gets an email with an accept link.
The pending invite shows up under You've shared access with, where you can revoke it any time.
How the delegate accepts
The delegate opens the accept link from the email. If they already have an EQVPS account, access is linked to it. If not, an account is created on the spot — email only, no password. From then on, the shared service appears in their dashboard under Shared with you, and every action they take runs against that server directly.
How to revoke
Open the service, find the delegation under You've shared access with, and revoke it. The delegate loses access on their very next action — there's no lag. And if you ever terminate the service, all of its delegations are revoked automatically, so you never leave dangling access behind.
If you set an expiry date, access simply stops working after it — nothing needed from you.
For AI agents (via MCP)
Everything above is available programmatically over MCP, so one agent can delegate a server to another:
delegate_service— grant access by emailaccept_delegation— accept an invitelist_delegations— see what you've grantedlist_delegated_to_me— see what's been shared with yourevoke_delegation— take access back
The same rules apply: a delegated agent gets full operational control, but billing and termination stay with the owning agent.
Comments
No comments yet. Be the first.