OPEN-SOURCE DEVIN CLOUD ALTERNATIVE

It asks before
it writes code.

Give Shiba a repository and a task. When deployed, review the exact plan before a sandbox starts by default, then follow the work in your Cloudflare account.

No hosted black box. Every task is approval-gated before a sandbox starts.

Retro desktop window of the shiba.workspace: harness chips, a pixel workstation, capability icons, and a status bar reading your Cloudflare account, one approval, six harnesses
USE FROMWebSlackTelegramDiscordGitHubMobile web is available; native iPhone app is on the roadmap.

TOOLS & MODEL PROVIDERS

Bring your tools. Keep control.

Five harnesses are supported — pick OpenCode, Claude Code, Codex, Devin CLI, or Grok, and run them with your own provider credentials.

OpenCodeINTEGRATED
Claude CodeINTEGRATED
CodexINTEGRATED
Devin CLIINTEGRATED
GrokINTEGRATED

Product names and logos belong to their respective owners. No affiliation is implied. See supported configuration →

TRIGGER FROM ANYWHERE

Trigger @shiba.
Get work done from anywhere.

SLACK · MOBILE WEB · TELEGRAM · DISCORD

Whether you are at your desk, on Slack, or on your phone, trigger @shiba to delegate a task. Review the exact plan, approve with one tap, and follow sandbox progress end-to-end.

● LIVE CHATOPS

Slack

@shiba fix the token refresh race in auth.ts↳ Generated plan ready for review

Trigger in any channel or thread. Approvals arrive as interactive Block Kit cards with diff previews.

● MOBILE WEB

Mobile web

Add to Home Screen · Standalone App↳ 1-tap review & sandbox approval

Mobile-optimized dashboard. Review proposed tool inputs, follow logs, and inspect diffs from anywhere.

● LIVE CHATOPS

Telegram

/shiba deploy staging hotfix --branch main↳ Webhook dispatch & inline buttons

Direct bot interaction with cryptographic webhook dispatch and inline button approval gates end-to-end.

● LIVE CHATOPS

Discord

/shiba task repo:backend issue:#142↳ Threaded run logs & diff previews

Slash commands and bot mentions for developer servers, with threaded progress updates and sandbox review.

The agent does the work.
You keep the keys.

ONE DEPLOYMENT · ONE CONTROL PLANE

An AI coding tool is worth exactly as much as the boundary around it. Shiba runs in your Cloudflare account, requires human approval before sandbox execution by default, and shows resulting changes instead of asking you to take completion on faith.

Why we built it

Why switch off a hosted agent.

SHIBA VS A MANAGED CLOUD AGENT

ShibaSHIBAManaged cloud agentMANAGED CLOUD AGENT
Runs in infrastructure you ownShibaYour Cloudflare accountManaged cloud agentThe provider's account
Model and harness per runShibaClaude Code, Codex, OpenCode, Devin, GrokManaged cloud agentChosen by the provider
Approval before code runsShibaRequired by defaultManaged cloud agentVaries by product
Who holds the credentialsShibaYou do, at egressManaged cloud agentHeld by the provider
LicenseShibaAGPL-3.0, source readableManaged cloud agentProprietary

What Shiba gives you

SIX PRACTICAL CAPABILITIES

01

Approval before execution

Review the exact repository, branch, task, and requested output. By default, no sandbox starts until you approve.

02

An isolated workspace

Each approved task runs in its own Cloudflare Sandbox container, separate from your Worker and other runs.

03

Work you can inspect

Follow agent progress, changed files, and a unified diff in the dashboard before deciding what to do next.

04

Your account, your controls

Self-host the Worker, choose your model route, and keep provider credentials outside the container.

05

Optional pull requests

Ask Shiba to open a branch and pull request when you configure a GitHub token; diff-only tasks need no token.

06

Chat and dashboard entry points

Start and review tasks from the dashboard, Slack, Telegram, Discord, or the mobile web app. A native iPhone app is on the roadmap.

From task to inspectable diff

THE APPROVAL GATE IS THE WORKFLOW

01 / CONNECT

Bring a repository

Paste an HTTPS GitHub repository URL and describe the coding task in the dashboard.

02 / DECIDE

Approve or reject

Inspect the proposed tool input. By default, Shiba waits for your approval before starting a sandbox.

03 / REVIEW

See what changed

Follow progress and review changed files and the diff. Publishing a pull request is optional.

BUILD WITH YOUR OWN AGENT

Put software engineer in your cloud.

Open source (AGPL-3.0), self-hosted, and yours to fork. It takes one command to run it against a repo you own.