Regnant / Case Studies / Brackett
Case Study. Brackett × Bubbly
Six websites.
One day.
Brackett is a private web design and development studio, small team, high standards, clients who expect speed without compromise. They deployed Bubbly on their own infrastructure and shipped six complete websites in a single day, each built to their design system, accessibility-compliant, and delivered without a single line of proprietary source ever leaving the building.
6
websites
shipped in one day
100%
on-premise
source never left the building
4
engineers
coordinated through Bubbly
0
cloud API calls
local models only
[Brackett studio workspace: multiple projects in parallel]
Brackett Studio. Bubbly deployment
Six concurrent workspaces
The challenge: 01
Multiple clients, same deadline. A design system that had to be enforced, not explained. And a mandate: proprietary source code cannot leave the studio perimeter.
Brackett had six website projects converge on the same delivery window. Each site shared the studio's design system but served different clients with distinct content, branding, and integrations. The traditional approach, serial execution, manual context switching, repeated explanations of component patterns: would have taken weeks. They needed parallel execution without losing control or sovereignty.
The deployment: 02
Air-gapped Bubbly.
Brackett deployed Bubbly in Posture 01. Air-Gapped. Local models via Ollama on studio hardware, no internet required, source code never transmitted. The design system lived in a shared monorepo; Bubbly indexed it once and referenced it correctly in every new project.
How it worked.
01
Parallel execution
Six concurrent projects, each with its own Bubbly workspace. Shared design system automatically enforced across every site.
02
Self-review before commit
Every changeset verified against accessibility standards, responsive breakpoints, and performance budgets before human review.
03
Context retention
Design tokens, component patterns, and brand guidelines indexed once, referenced correctly in every new site without re-explanation.
04
Human approval gates
Destructive operations, deployment steps, and third-party integrations all flagged for explicit approval. The team stayed in control.
Timeline comparison: 03
Before Bubbly
6 sites × 3 days each = 18 engineering days
Manual context switching, repeated explanations of design patterns, late-stage accessibility fixes.
With Bubbly
6 sites in 1 day = same-day delivery
Parallel execution, shared context, self-review before commit, zero source exfiltration.
In their words: 04
“We needed speed without sacrificing control. Bubbly gave us both, our design system enforced automatically, our source code never leaving the room, and our team approving every consequential step. Six sites in a day is the headline. The real story is we stayed sovereign while doing it.”
Engineering Lead · Brackett
The result: 05
Six websites
delivered same day.
All six sites went live on schedule. Each passed accessibility audits, performance budgets, and brand compliance checks. Brackett's design system was enforced automatically, every component used correctly, every spacing value consistent, every interaction pattern familiar. The engineering team stayed in control: every build step, every deployment decision, every third-party integration required explicit approval.
And throughout the entire process, not a single line of proprietary source code left the studio. No API keys transmitted to external services. No intellectual property exposed to third parties. Speed and sovereignty: together, not in tension.
System deployed
Bubbly.
Self-hosted coding agent: not a chatbot with autocomplete
An AI engineering teammate your security team can actually approve. Plans the work, edits across files, runs the tests, reviews its own changes: on models you host yourself. Your source code never leaves the building.