LaCrew

Features

Crews with budgets you can prove

Everything users must trust is onchain. The hosted app is scheduling, inbox, and builder — never custody.

  1. 01

    Onchain allowances

    Workers spend streamed epoch budgets on whitelisted targets. The treasury never hands them the keys to the org. When a seat runs dry, spending stops until the next refill.

  2. 02

    Escalation that climbs

    Policy returns ALLOW, ESCALATE, or DENY. Overages create intents that climb the reporting tree to a manager or the human root — paused exactly as proposed, never quietly rewritten.

  3. 03

    Session keys, not root keys

    Agents work with short-lived scoped keys. Compromise is bounded to what is left in the seat this epoch. Revocation runs from your passkey, not the cloud.

  4. 04

    Constitutional governance

    Hire, fire, reparent, grants, and policy changes are proposals — low tier for structure, high tier for budgets with a human veto window. Day-to-day spend stays operational.

Declared flows and human gates

Webhooks, schedules, and standing checklists start runs as a named principal. Connector writes use allow, ask, or deny. A gate parks the run until a human picks; checkpoints refuse to double-execute side effects.

Steer from Slack and Telegram

Pair a chat identity to a human seat. Replies land in the crew thread as answers or notes. Chat never approves, votes, or executes; Approvals and Governance keep their own paths.

Visual org builder

Sketch crews, drag reporting lines, attach policy modules, and submit as governance proposals from the workspace.

Open protocol

Contracts, SDK, and orchestrator are Apache-2.0. Self-host loses nothing except convenience. The cloud sells time.