Daniel rooted a Xiaomi Mi 8, dropped OpenCrabs into an Ubuntu chroot on the device, and pointed a Flutter app at it over ACP. Then the crab wrote an Android app, built the APK on the phone with aapt2, javac, d8 and apksigner, and installed it. No PC, no cloud, no Gradle, no SDK.

Alexey replaced his accounting operator with an AI accountant running on OpenCrabs. Faster, more transparent, cheaper, and it doesn’t take feedback personally. The whole thing runs at ₽3,000/month on a lean Docker stack.

Janina manages commercial and residential property in Moscow (apartments, offices, storage sections, ready-to-rent businesses) plus the books of a second company, entirely through one bot in Telegram. Meter readings in, invoices out, contracts reviewed, listings posted: a month of real client use, straight from the chat.

Two weeks building miidas.ru on OpenCrabs, an AI financier for SMBs. The hard part wasn’t the code. It was the three scenarios every small business client walks in with.

Alexey fired his assistant and handed the whole job to the crab: scan Telegram for new real estate leads, cross-reference the chats, agree on follow-up vs close, and send them in five minutes. The same takeover covers the invoice loop: OCR, banking app, manual approval, management accounting.

Alexey’s team dropped frameworks entirely. When code is this cheap, the overhead of learning and maintaining a framework isn’t worth it. They even used OpenCrabs to build evals for OpenCrabs.

Carlos Eduardo is a product guy, not a full-time dev, and app.heyiolo.com is now live, built almost entirely with OpenCrabs. He runs the whole thing from a Telegram chat around the clock: describe a feature, the crab plans, writes, tests, and ships it. Deploys to Hetzner, CI on GitHub Actions.

opryshok’s agent owns its own Trello board. It creates tasks, tracks them, and manages the board autonomously. The human tweaks the crab daily; the crab runs the backlog.

kaduzeras is building an app from raw ideas with CRABS, and calls it a milestone in learning. The agent takes an idea and carries it toward a working product.

Adi’s whole process runs through OpenCrabs: throw out an idea, the crab finds valid data, they research to a conclusion together, then the agent handles the actual building.

“Check whether tomorrow’s Azimuth flight was rescheduled.” Someone’s flying tomorrow, so the family-profile butler didn’t trust one source: it scraped the airline’s own ops feed from the schedule page, reverse-engineered the airport’s live departure board API by reading the page’s JavaScript, formed a codeshare hypothesis, then disproved it with actual departure history. Honest verdict: the flight was dropped from that day’s schedule, and the airline never published a reason.

Adi had his crab produce a five-page World Cup 2026 tournament report as a landscape PDF. Group stage to knockout, the R32 upsets, R16 results, today’s match preview, the quarter-final picture with odds, and a running “our forecast vs reality” tracker.

Adi’s crab turns one employee spreadsheet into print-ready payslips for a plantation company. Two layouts (a PDF per person, or two per page with cut lines), empty allowance rows hidden automatically, batched through 100+ staff. It even checked the law before adding a “valid without signature” note.

Adi told his crab to stop being the global default and act as a specialized motion-graphics identity. It opened an agent-to-agent collab with a video-knowledge agent called “onno” for references and beat markers, then built a Remotion film synced to a synthwave score it composed itself in pure Python.

Adi runs his crab as a QA partner that hunts bugs in OpenCrabs itself and files GitHub issues with file:line source citations. It found the Telegram ghost-button bug and handed over a phantom-tool-call telemetry report that became a merged fix.

Adolfo runs three companies on a single OpenCrabs instance with one brain. It manages every server, debugs production live with the team, builds the product stack, runs the daily standups, and tracks the ops, all at once across dozens of isolated sessions.

Every new feature and every fix in OpenCrabs is built by OpenCrabs. Adolfo’s crab develops, tests, and ships the very product it runs on, then improves itself on a schedule.

The crab built the entire Truelens product, backend and frontend, and builds the infrastructure, backend, and DevOps for HeyIolo alongside Carlos. Full-stack delivery from a chat: schema, API, UI, deploy.

When something breaks on Truelens production, the crab debugs it live in the Slack channel alongside the team, in real time. It takes the routine fixes so the CTO keeps the hard calls.

Two products, six environments, one crab keeping them alive: Truelens and Neura/OpenCrabs across dev, staging, and production. It deploys, watches the certificates, pings uptime, self-heals the web server, and verifies the backups, so nothing falls over quietly.

A production VPS went fully network-dead: no ping, no SSH, no HTTPS, while the hosting panel kept saying “running”. Alexey’s ops-profile crab worked the incident end-to-end: confirmed the outage from two independent vantage points, drove the provider’s own API from the shell, dug their newer v2 power API out of the docs repo, and pulled the smoking gun, the provider’s panel itself couldn’t reach the Proxmox hypervisor node. Then guest-side forensics after recovery, and a paste-ready escalation ticket in the provider’s language.

The crab runs the GitHub workflow: triage incoming issues, draft responses, track every PR and release, and keep the backlog honest. Adolfo reviews; the crab does the legwork.

estimertravaux.com turns renovation photos into itemized French-market estimates in seconds. OpenCrabs is the brain doing it all: vision analysis, SKU selection, pricing, planning, the whole SKU-to-budget pipeline, orchestrated as an autonomous agent.