Dagger: a new way to build CI/CD pipelines
There&#x27;s so much more to CI&#x2F;CD than the build definitions (e.g. dashboarding, log viewing&#x2F;retention, access control, manual interventions, secret management, test reporting, etc.) and while some of your points resonate very strongly with me (e.g. local builds), I can&#x27;t help but wonder what the endgame is here?<p>You&#x27;ve raised $27m to what? Give away a free tool for engineers to define their builds in? While they continue to use and pay for another service to actually run the builds? I assume you intend to replace the CI service at some point and move up the stack to monetize?<p>Without more transparency its easy to imagine something like...<p>Step 1. Drive uptake of your tool by selling people on the pitfalls of &quot;CI lock-in&quot;
Step 2. Introduce your own CI solution, which people can now easily switch to
Step 3. Lock people in