Destaris
Browse the docs

Bring your own auth

How Destaris uses your own credentials for AI, email, and providers.

Destaris orchestrates; you own the accounts. For anything that costs money or carries abuse risk, you bring your own credentials — and they stay on your machine.

AI vendors

AI steps run as your own already-authenticated CLI (Claude Code today; others over time). You're signed in once, as yourself, and Destaris uses that session. Your keys live in your environment and your OS keychain — Destaris never proxies them, and never sends them anywhere but the vendor whose key it is.

An optional Anthropic API key

By default, Claude agent steps bill the Claude Code subscription you're already signed into — the behaviour above, unchanged. If you'd rather bill your own Anthropic API account instead, Settings has an opt-in Anthropic API key field: paste a key, encrypted at rest on your device, and flip on "Use API key for agent runs." With both set, Claude agent steps spawn with that key instead of your subscription session; which models are available follows the key's own entitlements. It's off by default, only affects the Claude runner (Codex, Gemini, and Rovo runs are unchanged), and toggling it applies to the very next agent run — no restart needed. Clear the key at any time to go back to the subscription.

Email and other providers

The same principle generalizes. To send email, you connect your own provider (for example Resend or SMTP); the key goes in your OS keychain. Future provider nodes (SMS, chat) work the same way: you hold the account, Destaris drives it.

Because the account is yours, the per-message cost, the deliverability, and the abuse surface all sit with your provider — there's nothing for Destaris to meter, and no shared sending reputation to protect.

What this means in practice

  • Nothing custodied. Credentials never leave your machine.
  • No resold tokens. You pay your vendors directly, at their price.
  • No usage tax. A meter only ever attaches to a resource Destaris itself provides — never to running your workflows or to a provider account you own.