Pipelines and Builds, Nothing You Cannot Use Yet
sparki beginner 3 min read
What this means for you
Sparki is a CI/CD product, and customer copy names only what ships: pipelines and builds, with live build logs, each step run in its own isolated container. Deployments, quality scores and dependency or CVE scanning are on the page only as “Not available”. The old “build, deploy, scan, score in one tool” pitch is retired until those exist. Source: sparki-tools/platform-docs decisions/2026-10-15-launch-to-revenue-scope.md §1 and §6 (accepted); sparki.tools, read 2026-10-25.
The pitch
Define a pipeline, run it, watch every line of output as it happens. Each step runs in a fresh, locked-down container. Plans are flat and per workspace, with no per-seat pile-up. That is the whole claim. One caveat for anyone writing launch copy: on 2026-10-25 no build worker was provisioned (gate G9 open, /health reports workers: unconfigured), so builds queue but do not execute in production yet. The demo tenant’s builds are seeded data.
Who it’s for
Small teams that want a hosted CI they can read at a glance, and the marketer or founder who has to write about it without promising features that are still on the roadmap.
Proof points
- Customer copy states only shipped capability. Decision §6 bars any claim to replace or match a named competitor, and any “best on the market” claim, until a dated, sourced comparison exists.
- The landing page shows Deployments and Dependency/CVE scanning as “Not available” (live page, 2026-10-25). The web-app has a test that fails if deploy, rollback or approval-gate claims return (
honest-copy.test.ts). - The worker is built to run each step in a container with no host environment, dropped capabilities and CPU, memory and time limits (sparki-019). It goes live with G9.
- Scope is CI/CD only through the 2026-11-12 launch mission. The so1-io fold is a proposed decision and changes nothing yet (sparki-025).
mindmap root((Sparki today)) Pipelines stages and steps your images Builds live logs isolated steps Plans flat per workspace build-minute caps Not yet deployments scanning quality scoreneighbors on the map
- The Design Journal Is the Launch explaining why Sparki publishes a design journal each sprint