About
A software studio in Fort Lauderdale
We build and run our own products, and take on a few outside builds. Beside this is every product we run today, and where each one stands.
- ButlerCRMIn production
- NexusDialerIn development
- PolyHuntrLive
- AsteriaWeb live
- OverwatchIn production
- TraceKillLive
- JarvisMCPIn production
- JarvisNanoIn development
- BriefRoomLive
- FPLBenchLive
Studio
The facts
- Based
- Fort Lauderdale, FL; working remotely
- What we run
- Our products
- Outside builds
- Web apps, CRMs, Shopify and WordPress sites, AI workflows
- Ownership
- You own the code, data and credentials at handoff
- Who you talk to
- The engineers who build it
- Open source
- GitHub
Process
How we work
- 01
Realistic timelines
Production software usually takes months. We give you our estimate at the start and update it as the work moves.
- 02
We say when we disagree
If we think an idea will not work, we tell you why and suggest an alternative.
- 03
We train your team
We show your team how the system works so they can handle day-to-day changes themselves.
- 04
The simplest tool that works
If a spreadsheet solves the problem better than an AI model, we will say so.
How we work
How a change reaches production
The same five gates for our own products and for yours. Nothing reaches your customers on the strength of a demo.
- 01 · Isolate
Its own branch and workspace
Every change starts in a separate copy of the code, so work in progress never touches what is live.
git worktree add .worktrees/your-change - 02 · Build
Engineers with AI agents
Agents write and test code beside us. They hold no passwords: every call they make goes through our gateway, which checks it and logs it.
agent → gateway → policy · audit · call - 03 · Prove
Evidence, then review
Tests, before-and-after screenshots of the running app, then independent reviewers. It does not move on until no serious finding is left.
review: 0 high · 0 medium → pass - 04 · Ship
Deployed and checked live
The pipeline builds and deploys. Then we check the running service itself, not just a green build.
replicas 1/1 · image sha matches · health 200 - 05 · Watch
Checked every night
Each integration we run is tested against its provider every night, so a changed API is caught before your team notices.
nightly: each integration vs its provider