Skip to Content

Roadmap

What's coming next

Here's where Cadence.CI is headed next, in the order it's landing, from what's coming first to what's still queued up.

Recently shipped

  • Secrets management

    Shipped

    Secrets have a home of their own on Cadence.CI: dedicated storage, rules and access control, built on Mélodium's in-memory secret handling.

    See how secrets work
  • Caches, artifacts and renders

    Shipped

    Runs keep their caches, artifacts and renders in buckets you choose, with cache scopes and versions, and the results shown right in the run page.

    See the storage page
  • Run debug view

    Shipped

    Follow what happened inside a run with debug events recorded at the detail level you pick, read straight from the dashboard.

    See how runs are shown

Coming next

  1. 01Up next

    Windows and macOS support

    Spin up Windows and macOS machines straight from your cloud provider, on demand, the same way Linux runners already do. Building on Windows or macOS today? Self-provided runners and GitHub- or GitLab-hosted machines already have you covered, this adds native cloud spawning to match.

  2. 02

    Webhooks integration

    Trigger a pipeline the instant something happens elsewhere, and let other systems react the instant something happens in yours. Inbound webhooks kick off pipelines from external events; outbound webhooks broadcast run and pipeline status as it happens.

  3. 03

    GPU management

    See exactly how hard your GPUs are working. GPU-equipped machines already spawn for accelerated workloads, next up is visibility into their load: utilization and performance data for every GPU powering your pipelines.

  4. 04

    Specific spawn procedures

    Write a few lines of logic and let them pick your infrastructure for you. Small decision scripts choose the right machine or image for each spawn request from your Mélodium program, based on tags, available resources, compute price, and more.

  5. 05

    Job hosting

    Host the job itself on Cadence.CI, not just the runners that execute it, and trigger it straight from a webhook. No Mélodium program needs to be running elsewhere first to kick things off.

  6. 06

    Result panels per job

    A green checkmark doesn't tell you much. Renders already show what a run found in its page, from a coverage badge to a whole web application. Once jobs are hosted, each job gets a panel of its own, arranging its renders the way your project needs.

  7. Kubernetes
    07

    Native Kubernetes provider

    Pick a Kubernetes cluster as easily as you pick a cloud provider, including major managed offerings, beyond today's self-managed controller model.

  8. 08

    Additional cloud providers

    More clouds, same simplicity. Clever Cloud, OVH, Cloud Temple, Outscale, Oracle Cloud, Azure, and Google Cloud are joining Scaleway and AWS as supported providers.

Want to see one of these sooner?

Tell us which one matters most to your team, it shapes what we build next.