ANNANIKSANNANIKS

ENRUFR

Autonomous software delivery

An AI software office that ships real code — and never releases to production without your approval.

Not a chatbot demo. Annaniks runs the full delivery lifecycle — discovery, specification, build, review and staging — and stops at a human approval gate before anything reaches production.

  1. 01Discovery
  2. 02Specification
  3. 03Build
  4. 04Review
  5. 05Staging
  6. 06Owner approval
  7. 07Production
Every project moves through the same reviewable pipeline.Production ships only after an explicit, recorded owner approval.

What this actually is

A delivery pipeline, not a chatbot.

Annaniks turns approved requirements into documented, tested, reviewable and deployable software changes. Work happens in isolated environments, lands as branches and pull requests, and passes quality, review and security gates. The owner approves the documentation baseline, and approves again before production.

Compared to a chatbot demo

  • It opens real branches and pull requests, not sample snippets.
  • It runs quality, review and security gates before anything merges.
  • It stops at a human approval gate before production — every time.

How it works

The owner journey

Seven steps from a brief to a reviewed release. You hold the gate.

  1. 1

    Create a project and talk to a Product agent. Voice input is transcribed and always reviewed by you before it is sent.

  2. 2

    The system tracks facts, open questions, conflicts and decisions as they are gathered.

  3. 3

    It produces a versioned PRD, specification, architecture and plan. You comment and approve the baseline.

  4. 4

    The CEO orchestrator activates only the roles this project needs.

  5. 5

    Agents work in isolated containers and worktrees, opening branches and pull requests.

  6. 6

    Quality, independent review and security gates run automatically on every change.

  7. 7
    Hard gate

    Staging deploys and is smoke-tested. Production requires a separate, explicit owner approval.

Step seven never proceeds on its own. Production waits for you.

Control & trust

Control is the product.

These are system rules, enforced in code and audit — not promises.

  • Nothing sensitive happens without an approval

    No production deploy, DNS change, spend or external message runs without a recorded, single-use owner approval.

  • Immutable audit trail

    Security-sensitive actions are written to an append-only log that cannot be edited or deleted, even by a direct database client.

  • No mocks in production paths

    Fake success states and placeholder handlers are rejected by the quality gate. Production code does the real thing or fails loudly.

  • Fail-closed billing and mail

    Payments and email stay disabled until real provider keys are configured. The product never fakes a charge or a sent message.

  • Manual production deploy only

    Continuous integration runs automatically. Continuous deployment to production is a manual, owner-triggered action — never automatic.

The team

Twenty roles, activated only when needed.

Model routing, memory, budgets and audit are deterministic platform services — not "AI employees" you manage. Roles are launched per project, only when the work calls for them.

Strategy & product

  • CEO Orchestrator
  • Product & Business Analyst
  • Project Manager
  • Solution Architect / Technical Lead

Design

  • UX/UI Designer
  • Creative Designer

Engineering

  • Frontend Developer
  • Backend Developer
  • Mobile Developer
  • AI/LLM Developer

Quality & security

  • QA Engineer
  • Independent Reviewer
  • DevOps & Release Engineer
  • Security & Compliance Reviewer

Growth & support

  • Content & Localization
  • Marketing & Growth
  • Sales
  • Customer Success & Support

Research & assistance

  • Personal Executive Assistant
  • Personal Research & Decision Assistant

Built for real

Production-grade infrastructure.

The same stack that runs the platform, stated plainly for technical evaluation.

  • TypeScript monorepo — pnpm + Turborepo
  • PostgreSQL + pgvector
  • Redis
  • Temporal durable workflows
  • S3 / MinIO object storage
  • GitHub — source of truth for code
  • Docker Compose
  • GitHub Actions CI

Two surfaces

One platform, two audiences.

Platform owner

Telegram Mini App + Bot

The control center for GitHub, deployments, approvals, budgets and retention. Owner-only, authenticated through Telegram.

Clients

This website

Sign up, then a project cabinet: brief, chat, documents, estimate and start work. No platform operations are exposed here.

Scope

Deliberately scoped.

  • No HR, accounting, native mobile app, autonomous payments or autonomous outbound customer email in this release.
  • Notifications stay quiet by default — you are interrupted only when a human decision is required.
  • Everything the platform can do is enforced by permissions on the server; clients never hold authorization.

These are deliberate boundaries for this release, not missing features to paper over.

Start a project.

Create an account, describe the work, and see an estimate before anything begins.