Docs
Getting started
From sign-up to a governed, audited reply in a few minutes.
Quickstart
- Create your workspace. Sign up, and a workspace is provisioned for you automatically.
- Register an identity. Add an account you own (platform, handle, allowed actions, daily limits).
- Connect a session. Use one-click browser login (a real browser is streamed to you; you log in) or paste a cookie export. The session is captured and encrypted.
- Compose. Draft a reply. Guardrails evaluate it live and return a verdict.
- Approve & run. Risky actions wait for your approval. Dry-run anything; arm external sends only when you're ready.
- Audit. Every action and verdict is in the ledger, with evidence.
Core concepts
- Identity: an owned account/persona with a platform, status, maturity, allowed/blocked actions, daily limits, risk level, and product/topic fit.
- Guardrails: policies evaluated before generation and before execution: identity fit, limits, link policy, disclosure, fake-customer and payment checks, banned copy patterns.
- Approval: a human gate for first posts, promo links from young accounts, sensitive DMs, payments, and gray areas.
- Ledger: the append-only record of every action, its verdict, outcome, and evidence.
- Worker: a hosted browser that captures and relays your sessions, like your own private Browserbase.
The verdict: go, hold, stop
Every proposed action resolves to one of three decisions, which is the heart of the product:
- allow: low-risk, in-policy. Safe to send.
- approval_required / draft_only: a human decides, or it stays a draft (e.g. missing context).
- block: refused, with a reason (fake-customer, ban-evasion, spam, blocked action).
Connecting sessions
Tunneler captures the session of an account you log into yourself. There is no stored master password and no automated-login fingerprint. Two ways to connect:
- One-click browser login: a real browser opens on a worker and is streamed into your dashboard. You complete the login (and any CAPTCHA/2FA); the session is captured automatically.
- Paste / upload: export cookies with a browser extension and import them. Useful when you'd rather not relay a browser.
Captured sessions are encrypted at rest and scoped to your workspace. Disconnect any time from Settings.
Self-hosting
The engine, API, and browser worker are containerized. You can run the tunnels on your own infrastructure for a stable, consistent egress, while keeping the same guardrails, approvals, and audit log. Our self-hosting guide covers the compose files and environment setup.