01 · Zyan BuildA Web Studio in the Browser — IDE, AI Pair, Git, Templates.
Every project opens as a full workspace: an editor with a file tree and command palette, panels for briefs, images, tasks, and feedback, and an AI pair powered by Claude and Kimi. Git runs through the GitHub App — status, PRs, and merges without leaving the window.
~ workspace/every panel, one window
Code
Components
Images
Tasks
Requests
Feedback
Prompts
SEO
Brief
Git
Templates
Settings
// templatesTality · ProTech · Prime — full-source starters, ready to re-brand
- Browser editor with command palette — no local setup for the team
- Claude + Kimi prompts with project context and per-workspace spend controls
- GitHub App git ops: status, PRs, and merges from the workspace
- SEO mode flips the same workspace into the SEO Command Center
02 · SEOAudits Become Fixes. Fixes Become Pull Requests.
The SEO Command Center runs a crawl joined to Search Console and DataForSEO research, drafts the actual change against the site’s code, then routes it by risk — low-risk fixes apply below the floor you arm, structural ones open a pull request your team reviews. Every applied change lands in a rollback ledger.
01Detectcrawl · gsc · serp
02Draftthe diff itself
03Gaterisk tier
04PR & mergereview + checks
05Ledgerrevert path
- A versioned Strategy Center, red-teamed by a second model before it locks
- Findings carry a severity, an owner page, and a drafted fix — a queue, not a score
- Metas, alt text, and internal links can auto-apply below the floor you arm
- Autoblog writes from the locked strategy and submits every URL to Search Console
- Live branded client reports drawn from Search Console and GA4, not screenshots
03 · Growth suiteAds and the Leads CRM — Where Attention Becomes Clients.
Google and Meta campaigns sync into one workbench where the AI drafts staged change-sets with the reasoning attached. You approve, server-side guardrails enforce, and every captured lead — DMs, lead forms, website visitors — lands in a CRM built to turn it into a client portal.
Adschange-set stagedshift $15/day to the winning ad set2m
CRMauto-reply sentInstagram DM · new lead tagged4m
Adsapproved by Rileyguardrails passed · applied once6m
CRMlead convertedclient portal provisioned8m
- Google and Meta in one workbench — staged change-sets, never silent edits
- Server-side guardrails and a kill switch enforce every approved change
- Instagram DMs, Meta lead forms, website forms, and texts land on one lead record
- Workflows publish like releases — a running lead never has the graph edited under it
- Voice, cold email, and prospecting moved to /outbound
04 · OutboundVoice Agents, Cold Email, and Lists That Build Themselves.
Demand creation with a person in the loop: versioned voice agents that disclose themselves as AI and book mid-call, a drafter–critic pair that writes cold email worth sending, and prospect lists scraped from maps and the open web. Arm it for your workspace — nothing dials and no first touch sends until someone clears it.
voice agentsdisclosed as AI on every call
books the meeting mid-call
transcript on the lead record
cold emaildrafter writes from the brief
critic refuses unsourced claims
first touch waits for review
prospectingmaps + open-web scrape
fit scored, email verified
call brief capped at 9 facts
human gateA campaign cannot arm until preflight and approval pass, and first-touch email waits in a review queue.
- Agent versions ship like releases — draft, validate, publish; drafts never dial
- Voicemail conduct is scripted: leave the configured message or hang up
- Calling windows follow each lead’s timezone; opt-outs are recorded mid-call
- Sequences send from your own domains and mailboxes, with SMS steps via OpenPhone
- A real reply pauses the sequence and hands the thread to the CRM inbox
- Bring your own Twilio or Telnyx numbers — the calls dial from them
05 · Client operationsBranded Portals, Bookings, Invoices — The Client Side, Handled.
Every client gets a branded portal — on your workspace domain or their own — with projects, approvals, files, analytics, and messaging. Bookings sync to Google Calendar with Meet links, and invoicing runs through your connected Stripe account or as recorded external payments.
client_portalbranded · your domain or theirs · DNS-verified
bookingsGoogle Calendar sync · Meet links · reminders
invoicingStripe-connected · external payments recorded
messagingclient threads · team chat · realtime
work_hubtask board · shift schedule · time clock
- Branded client portals with approvals, files, and live analytics
- Bring-your-own custom domains with fail-closed DNS verification
- Scheduling with availability blocks, booking types, and reminder emails
- Work hub for the team: tasks, saved views, shifts, and time clock
06 · AI & AgentsClaude Code, Sandboxed Inside Your Workspace.
Not a chat box bolted onto a dashboard — a real agent runtime. Each terminal session gets its own bubblewrap-jailed machine on Fly.io with your repo mounted, typed MCP tools scoped to your workspace, and an approval gate wherever money or publishing moves.
terminal — avidautodetailing
$claude — session sandbox ready
»fix the canonical loop on /blog pagination
✓mcp seo.findings → 3 open findings on this project
✓branch seo/canonical-loop · 4 files changed
→pull request #217 — waiting on review
- A fresh jailed machine per session, with Claude Code and Codex at the prompt
- Tenant-scoped MCP servers expose your SEO context as typed tools — no global keys
- Headless jobs run in an isolated clone and come back as a draft at a gate
- Claude is the default; Kimi K3 is the budget lane, and headless publish is Claude-only
- Click-to-annotate turns a pin on the live draft into a bounded, diffable edit
- Voice input streams straight into the terminal — prompt it hands-free
07 · EducationA Studio Your Students Can Actually Ship In.
Cohorts build on production-grade templates from day one. Seats and permissions keep classes organized, and the activity feed gives instructors the real work trail — every edit, prompt, and commit, attributable to a student.
~ cohort/28 students · 12-week course
Templates
Seats
Permissions
Activity
AI pair
Reviews
Briefs
Portfolios
- Real client-grade sites instead of toy exercises
- Per-student seats with instructor-controlled permissions
- Discounted seats for colleges and bootcamps
08 · Admin & securityTenant Isolation, Granular Permissions, a Full Activity Trail.
Every workspace is isolated at the database layer with row-level security. Team access runs through a granular permission grid, realtime channels are locked to your tenant, and the activity ledger keeps an audit-friendly record of who did what.
tenant_isolationrow-level security · every table
permissionsgranular grid · 38 keys per member
realtimeprivate tenant channels only
custom_domainsDNS-verified · fail-closed
- Member-level permission grid across projects, billing, and clients
- Realtime channels are private to your workspace — no public topics
- Activity ledger across commits, prompts, and admin actions
- Full security posture at /security