Meteroid billing

Meteroid provides plans, prices, subscriptions, invoices, and metering. JumpCLI communicates with a fixed version of the Meteroid service through a restricted adapter layer, without modifying its source code or database.

Deployment boundary

• Meteroid uses a separate Compose stack and separate data volumes.
• Its HTTP, gRPC, and database ports are not exposed to the public internet.
• JumpCLI calls the service over an internal network and from allowed host/IP ranges.
• Billing credentials are supplied through environment variables or secret references and are not browser-visible.

Startup sequence

1. Copy the environment template in the Meteroid deployment directory and enter strong secrets.
2. Build any required extension images.
3. Start the services and wait for health status.
4. Run the Meteroid smoke test supplied with the project.
5. Set the Meteroid origin, restricted credentials, and allowlist in JumpCLI.
6. Restart JumpCLI and check billing readiness in the operator console.

Production validation

After creating an official organization, API token, draft plan, price, metric mapping, and test subscription, confirm that effective entitlements appear in workspace permissions. Do not expose a paid entry point to real customers if any step fails.

Before this production catalog is ready, use Free test plans to validate JumpCLI's login, credit, and generation paths. They do not call Meteroid's production usage API.

For details, see Plans and billing.