Free test plans

Before the Meteroid production catalog and payment service are ready, JumpCLI can explicitly enable free test plans for production-path validation only. They make real user journeys testable without presenting testing as a paid subscription.

Enabling conditions

Set the following in the JumpCLI server's .env:

BILLING_TEST_MODE=true
BILLING_TEST_PLAN_UNITS=20
BILLING_TEST_STARTER_UNITS=20
BILLING_TEST_CREATOR_UNITS=80
BILLING_TEST_STUDIO_UNITS=200

After rebuilding or restarting the application container, signed-in users see three free test plans on the subscription page: starter-test (20 units), creator-test (80 units), and studio-test (200 units). Activating one creates local image credits for the current UTC calendar month. When credits are exhausted, image generation returns an explicit insufficient-credit status.

What this does not do

• It does not create payment orders, charge customers, or collect payment methods.
• It does not write test generations to Meteroid's production usage API.
• It does not create Meteroid customers, products, prices, or subscriptions.
• It does not replace Alipay, a Meteroid API token, or production plan mapping.

Plan activation and credit changes remain in JumpCLI's local audit data. When email SMTP is configured, plan activation asynchronously sends a test-plan notification. BILLING_TEST_PLAN_UNITS remains the Starter-compatible fallback value for the legacy single test plan; the three new BILLING_TEST_*_UNITS settings can be adjusted independently.

Disabling and switching

Before production billing, create the organization, API token, products, prices, metrics, and plan mappings in Meteroid, then disable test mode:

BILLING_TEST_MODE=false

The system refuses to overwrite an existing non-test credit period. Complete migration through the operational billing process to avoid changing established credit facts or usage records.