Open source

The mapping rules engine wants to be a top-of-funnel asset.

The marketing plan calls for extracting the rules engine — tag, account, regex — as an open-source package. The interface is stable enough; the package cut is on the roadmap.

Tovin.io plans to open-source its cost mapping rules engine — the tag, account, and regex primitives that decide which cloud resource belongs to which project. The roadmap covers a dry-run preview contract, retroactive remap semantics tied to rule versions, and FOCUS-aligned field names so the engine plays well with other FinOps tooling. Until the package lands, the same engine ships inside the hosted product and is safe to try on read-only billing data.

✓ Read-only credentials   ✓ 90-day backfill   ✓ KMS-encrypted at rest

What gets shipped as open source

Tag, account, and regex rule model

The same primitives the SaaS uses. Stable enough to depend on, narrow enough to read in an afternoon.

Dry-run preview contract

Apply a candidate rule set without persisting — the same preview that powers the in-product UX. Designed to be safe to run on production data.

Retroactive remap semantics

Bind rules to a version, then remap all rows against the new set. Deterministic, auditable, idempotent.

FOCUS-aligned field names

Where practical, field names follow the FinOps Foundation's FOCUS spec so the engine plays well with other tools in the ecosystem.

Roadmap to the public package

  1. 01

    Stabilize the rule shape

    Tag, account, and regex matchers are stable in production. The interface needs to clean up its serialization before it becomes public.

  2. 02

    Lift the dry-run preview

    The preview engine already runs candidate rules over a sample of rows. Extracting it requires unlocking the rate-limited host-side validators.

  3. 03

    Adopt FOCUS field naming

    Where practical, field names align with the FinOps Foundation's FOCUS spec so the engine slots into other ecosystem tools.

  4. 04

    Ship under an Apache-2.0 license

    Permissive enough to embed in commercial tooling. The package ships with its own docs site and a CHANGELOG.

Until the package lands, the SaaS is the way to try it.

✓ Read-only credentials   ✓ 90-day backfill   ✓ KMS-encrypted at rest