Alpha · Honest expectations

What alpha means right now.

Sulis is in active alpha. The plugin works, and the path from idea to shipped backend is real — though some edges are rough. Here's how to join the one-month alpha, what to expect, and where those edges are.

Join the one-month alpha

You proved your idea with a prototype — the open question is whether the backend underneath can carry real customers. For one month I'm running hands-on sessions: you use Sulis on something real, I watch where you get stuck, and the gotchas you hit become my fix list. I'll address the rough edges as we go. If a session helps you, the best thank-you is telling another founder.

Claude Code installed
An open mind — Sulis works autonomously, and that's a shift in how you build

Book a session → Join the WhatsApp group

This is genuine alpha — not production-grade yet. Exactly what that means is spelled out below.

What alpha actually means

Alpha — for Sulis specifically — means three things:

The plugin runs the full lifecycle on real projects. Spec, design, build, review, secure. It's not a demo; it ships code.
The surface moves. Commands, defaults, and prompts evolve as we learn from real alpha sessions. A command name may change between versions.
You're not alone. Every alpha tester gets a direct line to me. If you hit a wall I haven't seen yet, I want to know within hours, not weeks.

Known rough edges

An honest, living list of things you'll likely notice. None of these block you from shipping — they just mean you'll occasionally have to work around them.

Known

Long sessions can lose context

A session running multiple hours may forget early decisions. Workaround: /sulis:status prints the journey state — paste it back if Sulis seems to have drifted.
Known

Brownfield analysis is conservative

On existing codebases, the discovery phase sometimes flags more than it should — better safe than missing real risk. You can override its findings; Sulis will record the override.
Rough

Some Phase 5 tasks block on convention questions

If your codebase uses an unusual convention (e.g. a custom test runner, a non-standard router pattern), Sulis sometimes pauses for confirmation rather than guessing. Tell it the convention; it'll remember for the rest of the session.
Rough

Command names occasionally rename between releases

If a /sulis:* command returns "not found" after a version bump, run /plugin list to see the current surface. Old names usually redirect for a release before being removed.
Known

No official platform yet

The plugin is what's available. The control plane (the part that operates your shipped app while you sleep) is in active build — see sulis.dev.

Getting help

There's one channel for alpha support, and it's direct:

Message me on LinkedIn

I read every message and reply within a day on weekdays. Tell me what you were doing, what you saw, and what you expected. Screenshots help. Especially valuable: anything that made you stop and re-read what Sulis said. That's the place where the plain-English layer is failing.

DM Iain on LinkedIn →

If you'd rather raise something in public — GitHub Issues on the agents repo works too. I read those daily.

What Sulis sees

Trust matters here, so this is exactly what runs where:

Reads your code Yes — Sulis needs to read the files in your repo to understand context, plan changes, and review what it writes.

Writes to your repo Yes — as Git commits in branches it tells you about. You review before merging.

Stores journey state Locally, in .sulis/{project}/JOURNEY.md. Stays in your repo; you can commit it or gitignore it.

Uploads code to Sulis servers No. The plugin runs entirely in Claude Code. There's no Sulis-hosted server. The platform (when it ships) is opt-in.

Sends telemetry No telemetry from the plugin during alpha. Anthropic's own Claude Code telemetry rules apply separately — see Claude Code's docs.

Trains on your code No. Sulis doesn't train models. Anthropic's policy on Claude Code training applies separately.

The promise. No lock-in. No black-box. Your git repo, your SDK, your code, always. If you stop using Sulis tomorrow, every artifact it produced — the spec, the architecture, the tests, the code, the security review — stays yours and stays usable.

Back to Docs overview →