What we have built.
This page is an honest record. Seros, LLC is a new company and has not yet shipped a client project, so there are no client logos or case studies here and none will be invented. What there is instead is a production-grade system we designed and built ourselves, which you can judge us on.
The in-house product
Our first build is an in-house product: a Slack-to-Linear delivery workflow. It reads only the channels an administrator explicitly selects, identifies the commitments people make in those conversations, drafts the corresponding tracker work, and refuses to write anything until a person reviews and confirms it.
What it demonstrates
| Capability | How it shows up in the build |
|---|---|
| Third-party integration | Slack OAuth with signed-request verification on every inbound event, and a server-side Linear client with its credential held only in production configuration |
| Multi-tenant isolation | Every query is scoped to a workspace, enforced by an automated check that fails the build if any module reaches past the scope boundary |
| Human-in-the-loop AI | A model proposes; a task row can only be created from a recorded human confirmation. There is no code path that skips it. |
| Auditability | Workspace actions are written to an audit log that database triggers make append-only, and every model call is metered against a per-workspace budget before it runs |
| Fail-closed operations | The application refuses to boot in production unless its required configuration is present and valid |
| Test discipline | Typecheck, tenancy check, offline unit tests and a scored evaluation set, chained into one verification command |
Status
The product is paused, not cancelled. Seros, LLC now sells AI consulting and build engagements rather than seats, so the product is not open for sign-up. The engineering stands on its own as evidence of how we work: written specification first, decision records for every irreversible choice, and a refusal to ship a path we cannot verify.
How we work, in four rules
- Nothing consequential happens without a person deciding it.
- Scope is written down before code is written, and the written scope wins.
- A claim we cannot verify does not ship, in software or in a status report.
- You own the code, the infrastructure and the credentials. There is no lock-in to us.