The software you need. Built around your rules.
Turn a business idea into a service your customers can use. Taiga carries the work through build, release and maintenance, guided by your company’s policies.
Let customers book their own deliveries.
Build the booking service, add rescheduling and keep it working with Taiga.
Discovery
Turn the request into a specification.
Your intent and published company policies shape the work.
Customers can book without calling.
Taiga builds. Your team reviews. Your pipeline deploys.
Now let them change their plans.
You put rescheduling in the queue. Taiga plans it.
The same booking. A new choice.
The reviewed change reaches the same production app.
Know how it is working.
URL checks and browser signals show how the service behaves.
A security fix joins the work.
The patch gets its own review and independent scan.
Customers keep booking. Your team moves on.
Monitoring continues
a17c942b28d153c39e264CurrentBooking confirmedDelivery rescheduled
Change delivery timeApp URL configured · browser beacon connected
Want to see it all?Continue here, at your pace.Close story
Start with the service your customers need.
Describe the business outcome. Taiga turns the conversation and your published company policies into a specification, then derives the remaining setup documents.
Your intent and your published company policies.
A self-service booking portal, built around your company’s rules.
Your team published the specification, then completed and reviewed the remaining required setup documents.
Your service opens for business.
Taiga builds against your rules. Your team reviews the result before it goes into production.
Your team reviews. Your configured pipeline deploys.
- Specification
- Queue and build
- Required review
- Configured pipeline
Your pipeline reported this successful production deployment. Taiga keeps the version and its deployment record together.
Customers want to change their plans.
Make rescheduling the next initiative. Put it in the queue: Taiga plans the change using your project context and company policies.
You choose the next improvement. Taiga plans it.
- INIT–02Let customers reschedule a delivery.Building
Keep the booking. Give customers a choice of another available time.
No work here
No work here
No work here
Build on its own · enabledMerge · required review applies
The initiative started in Backlog. Your team added it to Queue; Taiga planned the change before building it.
The improvement reaches your customers.
Your team reviews the change and your pipeline deploys it. Taiga records the version reported by your provider. The delivery portal now offers rescheduling.
Required reviews stay in force for every release.
- Reviewed
- Development
- Production
Your pipeline reported this successful production deployment. Taiga keeps the version and its deployment record together.
See how the service is working.
Availability, experience and browser-observed API errors and response times show what needs attention.
Availability, experience and API signals in one project.
Illustrative records and measurements. No live systems are connected.
The project has an App URL configured and a browser beacon installed. These signals describe the running service; repository findings are tracked separately in Maintaining.
A dependency needs a security update.Customers keep booking. Your team moves on.
Maintaining finds an urgent dependency risk. An eligible fix joins the queue, follows the configured build and review requirements, and receives an independent scan when its pull request is ready.
Repository finding → queued patch → review and independent scan.
When the fix pull request became ready, Taiga automatically started an independent scan of its branch. Here the scan no longer detects the advisory.
- Patch built
- Independent scan: advisory absent
- Required review completed
- Pipeline reported production deployment
The scan can report Fix verified, Still vulnerable or Could not verify. Required review and pipeline deployment remain separate steps.
The service is running, the improvement is live and the vulnerability has been resolved.
Illustrative workflow and metrics; no live system is connected. Eligible urgent dependency patches join the queue. Build and merge follow your configured permissions and review requirements. An independent scan checks the fix branch when its pull request is ready.
Fictional delivery business. Real Taiga interface patterns. The longer walkthroughs explain the technical decisions.
What would you put into production?
Bring an idea, an existing system or the change your team keeps putting off. We’ll work through the scope, your rules and a practical first step.
Your company’s rules are part of the build.
Your intent and published policies shape the specification. Approved technologies, data requirements and design standards guide each initiative.
Start where your software is.
You do not need a blank repository, or a finished specification, to start a useful conversation.
Evolve your software
Import your codebase. Turn its findings into prioritized work and take the next business improvement into production.
New software
Shape the user journeys and interface, then carry the idea through a controlled build into a running application.
Keep production healthy
Turn a production finding into a repair. Follow it through delivery, deployment and independent verification.
Know the cost. Choose who operates it.
Calculate your monthly service price, choose the operating model and use the Trust Center for security and procurement questions.
Questions we get from enterprise buyers
What does Taiga actually deliver?
Software you can shape, build, release and maintain: from a new specification or an existing codebase through user journeys, queued initiatives, reviewed changes, deployment and monitoring. The agreed hosting mode defines who operates the runtime. Product
How is this different from an AI coding assistant?
Taiga connects business intent and published company policies to the whole software lifecycle: specification, initiatives, implementation, review and operation. Coding agents can do the implementation within that workflow. Product
Is Taiga ISO 27001 certified?
Current status: no ISO 27001 or SOC 2 certification is claimed. Certification plans and the third-party penetration-test status are stated in the security FAQ. Review security and contracts
What does an engagement cost?
Learn starts at €2,000 per month. Learn with Deliver + Operate starts at €6,000 per month and includes 1,000 Aurora. Prices exclude VAT; scope and hosting responsibilities are agreed in your order. See pricing
Put your next business idea to work.
A new service, an existing system or a change your customers need. Bring it to the conversation.