Plans
Community does not create a Chydio subscription or recurring server cost. Local Unity automation remains usable without billing.
Intended for one user connecting securely to their own development machine. Not yet for sale.
Intended for paid seats, shared sessions, roles, approvals, and audit history. Not yet for sale.
There are no free trials, promotional subscriptions, complimentary hidden entitlements, or support-issued bypasses in the planned production model. Any future promotion must be explicit, time-bounded, auditable, and reflected in checkout.
Payment and merchant of record
Paid subscriptions are planned through Stripe Managed Payments. Stripe/Link acts as merchant of record for eligible transactions and handles the payment, receipt, order management, supported tax collection, and transaction-level support. Chydio owns product access and product support.
Checkout must display the charged currency, billing period, taxes, renewal date, and total before purchase. Stripe—not Chydio—collects complete payment-card details. Managed Payments availability and tax coverage vary by product and country, so an unsupported jurisdiction cannot be silently treated as covered.
Renewal and cancellation
Paid plans are intended to renew automatically for the interval shown at checkout until canceled. Users must receive a self-service Link order-management path to cancel. Unless the final checkout terms say otherwise, cancellation is intended to stop the next renewal while access continues through the already-paid period.
Deleting a Chydio ID is not a substitute for canceling a subscription. Final account-deletion flow must warn about and resolve any active subscription first.
Refunds, payment issues, and disputes
The final refund window and eligibility rules are not yet approved. They must be shown at checkout before paid launch. Transaction, receipt, duplicate-charge, payment-method, tax-document, and order-status questions route through the Stripe/Link order-management experience.
Product defects and access problems route to Chydio Support. A refund, chargeback, failed payment, or fraud hold may pause the paid entitlement while it is reviewed. Chydio support cannot ask for or accept full card numbers, bank credentials, identity-provider passwords, API keys, or CLI tokens.
Downgrades and access changes
Chydio checks paid entitlement online when a hosted session starts and periodically while it remains active. Cancellation scheduled for period end should not interrupt the current paid period. Expiration, refund, unresolved dispute, or failed-payment status can prevent new remote writes and move an active hosted session into a bounded safe shutdown.
Temporary network loss may use a short, signed grace lease; it is not indefinite offline paid access. Self-hosted models and local Community workflows remain local and are not disabled by a Chydio subscription ending.
Billing help
Use the Link receipt or order-management link for transaction and order questions. For a product entitlement mismatch, contact support@chydio.com with the Chydio ID provider, approximate purchase time, plan name, and Link order or receipt reference.
Never email a full card number, bank credentials, password, API key, recovery code, project, source file, prompt, or provider response. See the Support page for the low-data intake format.
Draft status: technical preview · Cancellation/refund and jurisdiction approval required before paid launch