Built-in template
Marketing
Turn a product brief into campaign drafts for your review.
Example outputs
- Launch brief
- Campaign copy
Open source · AGPL-3.0 · Self-hostedHire AI employees you own.
Hire AI employees you own.
Approve every move.
Shiba runs code, design, marketing and ops work in your own Cloudflare account. Brief it in Slack, review the plan, and nothing executes until you say so.
Free to self-host · hosting and model usage cost extra · coding tasks need a GitHub repository
Employees
Every department.
One workspace.
Four built-in templates: Engineering, Marketing, Research and Operations. Sales, Product, Design and QA are custom-role examples. Add your own instructions for any role.
Custom role example
Sales
Prepare account research and outreach drafts from supplied context.
Example outputs
- Account brief
- Draft outreach
Built-in template
Research
Answer a focused question with sources and gaps made clear.
Example outputs
- Research report
- Sources and open questions
Custom role example
Product
Turn customer evidence into a product brief your team can discuss.
Example outputs
- Product brief
- Scope and acceptance checks
Custom role example
Design
Map a user flow and draft interface copy before you build.
Example outputs
- Design specification
- States and accessibility checks
Built-in template
Engineering
Make a focused code change and report the checks run.
Example outputs
- Code changes and tests
- Review handoff
Custom role example
QA & Testing
Check a feature and document what passed, failed, or needs another look.
Example outputs
- Test report
- Reproduction steps
Built-in template
Operations
Turn a recurring process into a checklist someone can follow.
Example outputs
- Operating runbook
- Readiness and recovery steps
Custom role
Your custom role
Give an employee instructions for the work your team repeats.
You define
- Your working brief
- The files you need
Engineering, Marketing, Research, and Operations have built-in templates. The other roles shown here are examples you can create with custom instructions.
Roles use information you supply to prepare drafts. A role alone does not connect accounts, make payments, update external services, or grant permission to publish.
The approval gate
Autonomous,
not unsupervised.
Describe the task
Name the output: a code change, campaign draft, or account brief. Pick the repository or private workspace it works in.
Review the proposal
See the exact files, branch and actions before anything runs. Approve or reject the request.
Keep the decision
Shiba returns a pull request and checks. Publishing and sending stay a separate, human step.
Why self-host
Your employees shouldn't live
in someone else's account.
AspectHosted agent platformShiba
Source codeClosed, or source-availableOpen source, AGPL-3.0
Where it runsThe vendor’s cloudYour Cloudflare account
Before it actsVaries; often a setting you must findApproval on every proposed run
If the vendor changesYou follow their roadmap or leaveFork it. You hold the code and the data
CostSeats plus usageFree software; hosting and model usage are yours
Typical hosted-platform pattern, not a claim about one vendor. Verify any vendor against its own terms.
Trust
Capable by design.
Never in charge.
Only controls you can inspect in the source. No badges we haven't earned.
Approval before execution
Every proposed run waits for a human decision.
Runs in your account
Self-hosted on your Cloudflare account, not ours.
You choose where work happens
Coding tasks use a GitHub repository. File work can use a private workspace when artifact storage is configured.
Auditable source
AGPL-3.0. Read exactly what the agent can do.
Give the next task a clear place to start.
Free to self-host. Your Cloudflare account, your repository, your approval.