Skip to content

What is Taiga?

Taiga turns conversations into structured, policy-compliant specifications, and then plans and builds the work that follows from them.

You describe what you want in a conversation. Taiga produces a specification from it, derives the supporting documents (user flows, architecture, data flow, security and privacy assessments), slices the result into initiatives, and its agents implement them against your repository.

“Policy-compliant” is not a slogan here. Your organization records the industries you operate in, your languages and frameworks, and your clouds. Taiga builds a set of policies and an approved tech stack from those answers, and every industry you select adds its own regulatory controls.

Everything downstream is shaped by them: the specification, the architecture, the security assessment, and the plans the agents work from. This is why setting up the organization comes before creating a project.

A project in Taiga is organized as three continuous loops rather than a sequence of phases. They run in parallel, at different speeds, and feed each other.

Loop The question it answers What lives there
Learn Are we building the right thing? Discovery, and the project’s documents
Deliver Can we turn intent into production? Initiatives, agent runs, deployments
Operate Is it working in the real world? Maintenance sweeps, monitoring

You will see these three names in the sidebar of every project, so they are worth recognizing early.

  • People defining work. Product managers and delivery leads who write the specification and decide what gets built.
  • Administrators. Whoever configures the organization: policies, teams, access, and connections to your source control and clouds.
  • Engineers. Anyone reviewing what the agents planned and produced, or working alongside them in the same repository.

You do not need to be technical to use Discovery, and you do not need to have used Taiga before to review what it produced.