Plans and credits

DawForge sells access on a monthly or annual subscription plus optional credit packs. This page is the working summary; the authoritative pricing lives on dawforge.com/#pricing.

The three plans

Solo

A serious-trial tier. Enough surface to author maps and try Flow, capped tight enough that committed users will outgrow it.

• Up to 24 vendor libraries acquired at once.
• 1 map stored, up to 16 articulations per map.
• 1 map per day created from the knowledge base.
• 1 map download per day.
• 1 template stored, up to 32 tracks.
• 1 template import per day.
• 1 template download per day.
• 25 Flow articulation switches per week.
• 1 concurrent Flow session.
• Phone link disabled.
• AI assistant: pay-as-you-go from credit balance.

Chamber

The working composer's tier. Enough for full sessions and serious template management.

• Up to 64 vendor libraries acquired at once.
• 32 maps stored, up to 64 articulations per map.
• 8 maps per day created from the knowledge base.
• 4 map downloads per day.
• 8 templates stored, up to 128 tracks each.
• 4 template imports per day.
• 4 template downloads per day.
• 500 Flow articulation switches per week.
• 1 concurrent Flow session.
• Phone link enabled.
• AI assistant: pay-as-you-go from credit balance.

Orchestra

Studio tier. No structural caps on the things you'll bump into in normal use.

• Unlimited vendor libraries.
• Unlimited maps, unlimited articulations per map.
• Unlimited maps per day from the knowledge base.
• Unlimited map downloads per day.
• Unlimited templates, up to 512 tracks each (the bridge script's pre-bound slot pool).
• Unlimited template imports and downloads per day.
• Unlimited Flow switches.
• 2 concurrent Flow sessions (useful for engineer + composer setups).
• Phone link enabled.
• AI assistant: weekly credit grant + pay-as-you-go.

What credits are for

Credits are consumed by two kinds of action:

1. AI-assisted features. Asking Maestro to find libraries or answer orchestration questions costs credits per message, billed by token count. Orchestra includes a weekly token grant; lower tiers buy packs.
2. Quota extensions. Each daily cap is individually extendable — buy extra units on demand instead of waiting until midnight or upgrading your plan.

Credits are deducted atomically — the balance check and deduction happen in the same database transaction so a failed request never leaves you out-of-pocket. Refunds are clawed back automatically via a reverse transaction.

Credit costs per action

Extending a cap mid-day

If you hit a daily or weekly cap and need to keep working:

1. Go to /settings/usage.
2. Find the dimension that's capped (it shows a red indicator).
3. Click Extend — this deducts the credit cost above and immediately grants you additional quota for the current period.
4. Extensions are persistent — unused units carry forward until you use them (they don't reset at midnight).

Alternatively, when you hit a cap mid-action, the app shows an inline prompt to extend directly from where you are.

Buying credit packs

Buy packs from /settings/billing in the app. Packs are one-off purchases; they don't auto-renew. They sit in your balance until consumed and don't expire at billing-period rollover.

Upgrading and downgrading

• Upgrade: takes effect immediately. The next period bills at the new tier; the current period is prorated.
• Downgrade: takes effect at the end of the current period. Until then, all features of the old tier remain active. After rollover, any over-cap state is grandfathered (you keep your existing maps / templates / libraries; you just can't add more until you're back under).

Concurrent Flow sessions

The Flow concurrency limit counts active browser tabs running Flow against your account. Opening Flow in two tabs on the same machine = two sessions. Solo and Chamber permit one; Orchestra permits two. The limit exists because each session holds open a Web MIDI port + a server-side state subscription. Closing the tab or letting it sit idle long enough for the connection to time out frees the slot.

Account closed / payment failed

A failed payment marks the account pending_tier until resolved. While pending: existing data is read-only; no new maps / templates / Flow sessions. Resolve the payment from /settings/billing and you're back instantly.

Next

→ Billing