Skip to main content

Plans overview

Plans are the packaging boundary that turns catalog resources into enforceable commercial behavior.

At a high level:

  • Catalog defines what exists: feature families, features, and meters.
  • Plans define what an account can do: entitlements, limits/policies, and pricing intent.
  • Assignment makes the plan effective for a billing account over time.

Vluna supports two common plan-source patterns:

  • Direct plan assignment (sales-led).
  • Provider self-serve (checkout and portal flows).

Prereqs​

What is a billing plan​

A billing plan is a sellable package that can be assigned to a billing account.

What a plan typically includes:

AreaExamples
entitlementswhich feature families are allowed
limitsquota and rate policy intent
funding designincluded credits/grants and plan-linked value strategy

Plan-centered wiring:

  1. Access chain: plan -> entitlements -> feature family/feature
  2. Feature-to-meter chain: feature family/feature -> meter_code
  3. Pricing chain: meter_code -> meter pricing baseline (+ optional contract-term-based pricing) -> priced outcome
  4. Enforcement chain: plan -> limit intent -> gate policies -> runtime decisions

Choose a plan source​

Before choosing a source, define your pricing model baseline:

Your backend assigns an effective plan to a billing account for a window.

See:

Provider self-serve (optional)​

Your frontend uses checkout and portal flows and the provider becomes the purchase source of truth.

See:

Next​