Your software factory. Without building the factory.
You want to build software around your business. You can also build the factory that produces it—or use Taiga and put that effort into the software you need.
Less stitching tools together. More moving software forward.
Requirements in one place. Tasks in another. Code, checks and production somewhere else. Taiga brings that work into one connected lifecycle.
Choose a stage to see what comes together
Carry the plan into the implementation.
Work spread across- Task planning
- Coding-agent sessions
- Progress handoffs
Plan an initiative, implement the change and keep its progress connected to the project context. Review the resulting work in your delivery workflow.
Your repository remains connected. Taiga does not replace every use of an IDE or your organization’s issue tracker.
Your repository · Deployment pipeline · Cloud · Identity provider
Tool categories show the work being consolidated, not a promise to replace every feature of a standalone product.
One ambition. Three ways to get there.
The decision is how to acquire and maintain your software delivery capability. Your business software is what it produces.
Who keeps the factory moving?
Look beyond the first implementation. Compare the ongoing work and agree the scope each option actually covers.
| Decision | Build in-house | Commission a factory | Use Taiga |
|---|---|---|---|
| Getting started | Design, build and connect your platform. | Scope a delivery project and acceptance criteria. | Check fit, configure the service and agree the first scope. |
| Factory development | Your platform team owns the roadmap and upkeep. | Your team or partner, under an ongoing agreement. | Taiga develops the platform; you assess its fit as your needs change. |
| Cost to plan for | Engineering time, models, infrastructure and ongoing support. | Build contract, change requests, running costs and support. | Service plan, usage and your team’s adoption and review work. |
| Room to tailor | Set your own architecture and development priorities. | Specify the design and negotiate how changes are delivered. | Use the supported workflows and configuration; assess specific requirements before committing. |
| Continuity and exit | Maintain documentation, skills and the ability to keep the platform running. | Agree ownership, handover, access and support terms. | Review repository and hosting choices, export needs and contractual exit terms. |
Getting started
- Build in-house
- Design, build and connect your platform.
- Commission a factory
- Scope a delivery project and acceptance criteria.
- Use Taiga
- Check fit, configure the service and agree the first scope.
Factory development
- Build in-house
- Your platform team owns the roadmap and upkeep.
- Commission a factory
- Your team or partner, under an ongoing agreement.
- Use Taiga
- Taiga develops the platform; you assess its fit as your needs change.
Cost to plan for
- Build in-house
- Engineering time, models, infrastructure and ongoing support.
- Commission a factory
- Build contract, change requests, running costs and support.
- Use Taiga
- Service plan, usage and your team’s adoption and review work.
Room to tailor
- Build in-house
- Set your own architecture and development priorities.
- Commission a factory
- Specify the design and negotiate how changes are delivered.
- Use Taiga
- Use the supported workflows and configuration; assess specific requirements before committing.
Continuity and exit
- Build in-house
- Maintain documentation, skills and the ability to keep the platform running.
- Commission a factory
- Agree ownership, handover, access and support terms.
- Use Taiga
- Review repository and hosting choices, export needs and contractual exit terms.
What would it cost your team?
Explore two different decisions: acquiring a factory, and delivering software with it. Replace the example assumptions with your own numbers.
Factory example: the internal effort to build and maintain the factory versus using Taiga. Business application delivery work is excluded from both effort estimates. A Taiga plan also includes delivery capacity, so confirm the scope and fit.
Illustrative assumptions · EUR, excluding VAT
Selected service: Start · 1 product(s) · €6,000 / month · 1000 Aurora included
Build your factory
Over 12 months€456,000- People
- €432,000
- Other costs
- €24,000
Taiga + your team
Over 12 months€156,000- Taiga service
- €72,000
- People
- €72,000
- Other costs
- €12,000
Modeled difference over this periodTaiga scenario is €300,000 lower
Edit the example assumptions
Choose the Taiga service capacity
These starting values are examples, not observed results or delivery estimates. A lower labor budget does not necessarily mean a cash saving. Neither the service plan nor this calculation guarantees equivalent output or completion within the period.
Each total = months × (monthly hours × hourly cost + other monthly costs + any Taiga service fee). Include hosting, model use and amortized setup costs in other costs where applicable; do not add consumption already included in the Taiga plan again.
Your inputs stay in this page. They are not saved or sent with an inquiry.
Check capacity and pricingSometimes, building is the right investment.
Your factory may be a source of competitive advantage in its own right. You may need a specialized environment or a delivery model an external platform cannot support. A dedicated team and a long-term roadmap can make building a deliberate choice.
Does owning the factory’s development create value for your business?
If it does, price that commitment. If your priority is the software the factory produces, start by evaluating an existing service against a real piece of work.
A shared platform. Your business direction.
Agree the service scope and hosting mode before work begins. Using a factory still takes your team’s context and judgment.
You set the direction
Define the outcome, provide company policies and system access, and decide what to accept. Your team keeps the decisions that require its judgment.
Taiga develops the factory
Learn, Deliver and Operate connect discovery, implementation and review with monitoring and maintenance. Capabilities depend on configuration and the agreed service scope.
Agree who runs what
Choose your own repository and cloud, or Taiga Complete for a Taiga-provided repository and runtime. Application responsibilities follow that choice.