Bring your own keys

Included out of the box

There are no key fields on the deploy form. Where the platform covers a capability it works immediately, partitioned to your instance (your own memory space, your own inbox, your own desktop):

• Realtime voice — the speech-to-speech voice orb.
• Long-term memory — remembered facts with a nightly-maintained profile.
• App integrations — Gmail, GitHub, Notion, Linear, and a thousand more.
• Agent email inbox — an address of Pluto’s own.
• Cloud desktop — a persistent computer Pluto can see and operate.
• Web search — search results and page reading, PDFs included.
• Payments — buy things with a card of Pluto’s own.

Capabilities the platform does not cover stay off. If you need one enabled, ask the platform operator.

Using your own keys

Switching an instance onto your own keys — for example putting model usage on your own provider account — is handled by the platform operator; just ask. If the platform was metering your usage, metering ends as part of the same switch, so you are never billed twice (see Billing & credits).

Sign-in stays on your deploy account by design. If your team needs the instance gated by its own auth system instead, ask the platform operator — it’s supported, just not self-serve.