From vibe to viable.

Plugin in alpha · Platform on the way

A real production layer for your AI-built app.

Prototypes built with Lovable, Bolt, or Replit aren't broken — they did their job: proving a market. The harder question comes after: who builds the real version. Sulis is a senior backend team in your Git repo — a Claude Code plugin you install today. Open-source. The platform that operates your shipped app is on the way.

What we're building

What's available now. What's coming next.

Sulis is one stack with three parts. The plugin ships today — open-source. The SDK and control plane are in active build. Each part stands alone; together they take a validated prototype through to a production-grade backend without you hiring a development team.

The SDKComing soon
9 domains. 172 operations.
Auth flows, billing, GDPR consent, custom roles and org groups, async compute for long-running jobs (crawling, data processing, model training), workflow orchestration, AI-native observability, secret rotation, custom domains. Months of backend engineering, productised. Proven inside Sulis's own stack today; opens to the public with the platform.
The PluginAlpha · Available now
A senior backend team in your terminal.
A senior backend engineer and backend-savvy product managers, installed as a Claude Code plugin. They spec, design, build, review, and ship — in your repo, with your SDK. Available the moment you install — no headcount, no recruitment. Open-source today at github.com/sulis-ai/agents (MIT).
The Control PlaneComing soon
Runs your app while you sleep.
Ambient observability. A background agent self-heals known issues and only wakes you when judgement is needed. The default state is calm.

The plugin, in action

Plain English in. Production-grade backend out.

You install Sulis as a Claude Code plugin. From the same terminal you already use to build, you describe what you want in plain English. Sulis reads what's there, names what's missing, and ships the fix into your repo as a commit you can review. Nothing changes without you reviewing.

~/my-saas-app · claude --agent sulis:sulis
You

Add a payments page with Stripe and user accounts.

Sulis

Read the repo. 23 files · 47 patterns · 12 dependencies.

Before I add the payments page, three things in the existing code I'd want to fix first — they'll trip up the new code too.

Auth tokens aren't validated

Anyone with a forged token can act as any user. The /payments endpoint trusts whatever the cookie says.

No observability on payments

If a Stripe charge fails in production, the first signal is a customer email — not the logs. No traces, no alerts, no rate limit.

GDPR consent flow missing

User emails are being stored for receipts without an explicit consent flow. For EU-facing products, that's a fine larger than the runway.

Sulis

Walk you through fixing the auth first?

You
You're in control. Sulis surfaces production gaps in plain English, writes the fix, and lands it as a commit on a branch you review. Nothing merges without you. The artifacts — spec, architecture, tests, code, security review — are yours. Every action logged. Every action reversible.
Get started with the plugin →

The SDK, in action Coming soon

Months of backend engineering, in one import.

Nine domains, 172 operations. Auth, billing, GDPR consent, observability, async compute, custom roles, secret rotation, workflows, custom domains — the boring-but-critical work that an engineer would spend months wiring up, handed to you as a single typed SDK called from a few lines of code.

api/onboarding.ts
// New user signs up with email + receipt consent, // gets charged for their plan, and enters the welcome workflow. const user = await sulis.auth.signUp({ email, consent: ['marketing', 'receipts'], }); await sulis.billing.attachCustomer(user.id, stripeToken); await sulis.billing.subscribe(user.id, 'pro-monthly'); await sulis.workflows.run('welcome-sequence', { userId: user.id, });
4 domains used · 9 lines of code · ~14 days of engineering, saved
What this saves you. The SDK is what you'd otherwise pay a backend engineer months to set up and wire together — auth tokens that are validated, GDPR consent that's logged for audit, billing that's idempotent, observability that surfaces failures before customers do. It's the boring-but-critical production layer, productised. Proven inside Sulis's own stack today; opens to the public with the platform.
Explore the SDK reference →

After you ship

Wake up to confirmation, not a fire.

Once your app is live, the control plane is your morning check. A background agent watches the system, self-heals known classes of issues, and only escalates when something needs a human. The default state is calm.

app.sulis.dev / my-saas-app
All Clear 07:31
Users
428
+12 this week
Requests
12.4K
steady
Revenue
£2,140
+18% WoW
Storage
62%
of plan
Nothing requires action
  • Execution error in notification-worker, agent restarted service, success 03:42
  • Storage at 60%, agent scaled provisioned size by 25% 05:18
  • New customer signed up — acmecorp.com 06:09
The morning after you shipped a new feature. The agent handled two real incidents while you slept — restarted a failing worker and scaled storage proactively. The attention queue is empty because nothing needed a human. That's the product.

Who's building it

I've been building production systems for 20+ years.

I moved from South Africa to the UK with nothing — my first job was stuffing envelopes. Technology got me out, and I've spent the last 20+ years building production systems for enterprises that couldn't afford to break. Sulis is what happens when that experience becomes a platform anyone can call. If you're building something with AI tools and you're stuck on the production side, I'd love to hear about it.

Iain Niven-Bowling · Founder, Sulis · Bath, UK

Get in touch

The plugin is available today. The platform is on the way.

You can install the plugin in Claude Code now. The platform — the part that operates your shipped app while you sleep — is in active build. If you've validated a market with an AI-built prototype and you're weighing what comes next, message me directly and tell me what you're working on. The earliest users get the most attention.

Install the plugin → Connect on LinkedIn