// your server · your Claude · your phone
File a ticket from your phone. Your Claude ships it on your server . Your own AI developer — on your infrastructure, your subscription, all your projects. It works while you sleep; you approve when you wake up.
Free. Bring your own server and Claude subscription.
9:41
new ticket · acme-app
repo: acme/app bug
acme-app agent online · ubuntu-24.04 · fra1 queue
WF-142 Password reset link expires too fast Queued
Queued waiting for an agent slot 00:00
APPROVAL Merge fix/reset-token-ttl → main
server/auth/reset.ts +12 −3
lib/tokens.ts +6 −1
tests/reset.spec.ts +14 −0
Request changes Approve
MERGED · DEPLOYED ✓ #218 → main · 4a91c2e acme-app.weaveflow.app
WF-139 Add rate limit to invite endpoint Deployed
WF-137 Nightly export job report Deployed
simulated product interface · hover to pause
Your server Any Ubuntu box, any provider. We never hold your SSH keys.
Your Claude subscription No token markup, no per-seat AI fees. More model subscriptions later.
It works while you sleep Queued tickets, one inbox, approvals when you wake up.
01
Ticket
You write what needs doing. From your phone, in a queue.
02
Agent works
One agent per repo, on your box, next to your running app with real data.
03
You approve
A diff, a question, a decision. It waits in your inbox until you get there.
04
Deployed
Merged to main, shipped to your server, rollback one click away.
Feels like the tracker you already know — except the assignee writes the code.
// agent at work
It reports like a colleague. Short summaries, real diffs, and it asks before anything risky.
WF-138 Add rate limit to invite endpoint NEEDS YOU
agent 4m ago · 3 commits
Rate limiting is in on the invite endpoint — 10 per minute, per organization.
— New middleware on POST /invites , counted per org in Redis.
— Existing invite tests updated; 3 new cases cover the limit and the reset window.
— No schema change, so nothing to migrate.
FILES CHANGED · 3
server/routes/invites.ts +34 −6
server/middleware/rate-limit.ts +58 −0
tests/invites.spec.ts +41 −2
QUESTION
The limit is per organization. Logged-out invite accepts have no org — should those be limited per IP as well?
Per org only Per org + per IP Approve & resume
// inbox
One queue, every project . Answers, approvals and failures from every repo land in one place and wait for you. Nothing pings you at 3am; it's still there at nine.
inbox 3 waiting · 3 projects all approvals failures
acme-app WF-142
Password reset link expires too fast
Approval waiting — merge fix/reset-token-ttl , 3 files, +32 −4
2h ago Review
lantern-crm WF-091
Nightly export job kept timing out
Finished — batched the export, cut runtime 14m → 40s. Deployed.
6h ago Read
inkwell WF-047
Deploy failed — migration lock timeout
Rolled back to e1f7d90 . App is up. Agent paused, waiting on you.
8h ago Open log
// foundation
Live in five minutes. A new project starts as a real application on a real domain — not a scaffold you have to finish before the agent has anything to work on.
login + roles multi-tenant orgs database wired app shell HTTPS + domain deploy + rollback
https://acme-app.weaveflow.app/login
Acme
Sign in
you@acme.com
••••••••••
Continue
Forgot password?
// the honest comparison
Why not just run Claude Code from your phone? REMOTE TERMINAL APPS
× One session at a time, one repo at a time.
× A sandbox with a cloned copy — no real data.
× Nothing deploys. You still open a laptop to ship.
× Every project keeps its own scrollback. You are the router.
WEAVEFLOW
✓ Every project in one coordinated queue, one agent per repo.
✓ Runs next to your running app, with real data.
✓ Branch, PR, deploy and rollback are part of the loop.
✓ One inbox holds everything that needs a human.
Access was never the problem. Coordination is.
// pricing
Free to ship. Paid to delegate. Monthly Yearly
FREE · SHIP
$0 forever
The platform on its own. Complete, useful, no agent required.
✓ Create projects
✓ Deploy to your own server
✓ Free subdomain + HTTPS
✓ Push-to-deploy CI/CD
Start free PRO · DELEGATE
$29 /mo
Everything in Free, plus the agent loop.
✓ File tickets from anywhere
✓ Agent dispatch, one per repo
✓ The cross-project inbox
✓ Approve-to-PR
Runs on your Claude subscription — we never meter tokens.
Create your project The only other cost is the box itself — a ~€5/mo server from any provider, billed by them. Price shown is a placeholder. Weaveflow runs under your own Claude account, for your own work — one person, one subscription.
// trust
We never hold your SSH keys The agent on your box dials out to us. Nothing dials in.
Credentials encrypted per org What you do give us is sealed with a key scoped to your organization.
Any Ubuntu box, any provider Hetzner, DigitalOcean, a spare machine in a cupboard. Your call.
Self-host option Run the control plane yourself if that's the bar you have to clear.
We won't claim we store nothing. The honest line: you can run this without giving us any key.
ONE-LINE INSTALL
$ curl -fsSL weaveflow.io/agent | sh
git-based a real repo you own branch + PR workflow rollback on one command
Your first ticket is waiting . Point it at a server, connect a repo, and write the thing you keep meaning to fix.
Create your project Free. Bring your own server and Claude subscription.