- The personal free edition already supports self-serve order creation for local script slots, checkout-session creation, mock-payment success, and auto-activation after callback.
- The billing page can already show the current order, lifecycle summary, reconciliation summary, and recent payment callbacks.
- The
publicsuper-admin side already supports order creation, payment confirmation, callback activation, renewal reminders, expiry shutdown, and recovery. - The free path already exposes monthly and annual team-edition registration entries, while formal payment and formal tenant usage continue on the target tenant side.
Payment & Membership
Payment and Membership for the Personal Free Edition
Payment StatusTwo payment paths can now be described clearly in public: self-serve local script-slot expansion for the personal free edition, and the monthly or annual registration path that moves from the personal free edition into the formal standard-SaaS tenant entry.
This page answers four things: how the personal free page handles payment, how monthly or annual membership is registered, what users get after upgrading, and which parts are finished versus still unfinished.
If you are still exploring individually, prioritize personal billing and script slots. If you are preparing to enter formal collaboration, prioritize the monthly or annual team-edition entry instead of keeping formal billing and formal usage inside the hidden personal-free tenant.
Personal-free paymentMonthly team editionAnnual team editionFormal standard-SaaS tenantCurrent boundary is explicit
- The personal free page should not be described as a complete general payment center.
- The current payment line should not be described as already fully connected to formal third-party gateways.
- The free path should not be described as already closing the full registration, payment, activation, and renewal loop for formal team tenants by itself.
- The monthly or annual price of formal tenants should not be fixed on this page, because final pricing and payment handling should follow the target tenant registration page itself.
Path 01
Paying for local script slots in the personal free edition
- Local script slots +1:
19.90 CNY - Local script slots +3:
49.90 CNY, currently the default recommendation - Local script slots +5:
79.90 CNY - After payment succeeds, the local script-slot quota is written back immediately.
Path 02
Registering monthly or annual team-edition membership
- Monthly team edition: best when you want to start formal collaboration first and decide the longer cycle later.
- Annual team edition: best for teams already sure they will use ExecFabric long term, and currently the default recommendation.
- Both paths jump into the formal standard-SaaS tenant registration page, which is currently carried by the shared-tenant frontend instead of remaining inside the hidden personal-free tenant.
Authority
Which page is authoritative for pricing and payment
- The local script-slot prices in the personal free edition follow the three fixed packages above.
- The final price, payment page, and formal service cycle of monthly or annual team plans should follow the target formal-tenant registration page.
- If you need an enterprise edition, private deployment, or custom delivery, it is still better to discuss the scenario directly than to go through this standard page.
How To Pay
How the personal free page handles payment
Steps
01. Log in to the personal free edition
Enter the personal-free workspace and open the Personal Billing and Script Slots page.
02. Choose a script-slot package
Pick one package from
+1 / +3 / +5. The current recommendation is +3.03. Create an order and launch checkout
After the order is created, the page generates a payment session, payment-provider summary, and mock-checkout code.
04. Finish payment
The default path is the mock checkout. If the current environment is not convenient for mock payment, manual confirmation remains as a fallback.
05. Quota is written back and usage continues
After payment completes, the system confirms the order automatically, increases the local script-slot quota, and marks the order as activated.
What you get after paying
- You can continue uploading more local scripts inside personal free space without switching into a formal tenant first.
- The personal exploration path around Script Upload, Execution History, Announcement Center, Personal Space, and the CLI guide can stay continuous.
- This path is a better fit for expanding individual capability first, not for moving directly into formal multi-user collaboration.
- This payment only purchases local script slots. It does not mean a formal team or enterprise edition has been activated.
Monthly / Annual
How monthly or annual membership registration works
How the monthly route works
- From the Upgrade to Formal Version page in the personal free edition, click Go to Monthly Activation.
- The system jumps to the formal standard-SaaS tenant registration page carrying
source=personal_free_upgradeplus the monthly plan parameters. - This path is best when a team wants to verify one month of real collaboration first before deciding on a longer cycle.
- Later the user can still renew or shift into a more stable annual rhythm.
How the annual route works
- From the same page, click Go to Annual Activation.
- The system jumps to the same formal standard-SaaS tenant registration page, but with annual plan parameters instead.
- This is best for teams already sure they will use ExecFabric for the long term.
- The advantage is a more stable formal service cycle and fewer repeated monthly renewal operations.
What you get after registration
- A formal tenant workspace instead of staying inside the hidden-tenant semantics of the personal free edition.
- A better base for members, roles, shared Skills, approval, and governance capability.
- A smoother route into private deployment, intranet access, Local Agent use, or stronger audit requirements if those boundaries matter later.
What matters right now
- This page explains how registration works and why an upgrade makes sense. It does not promise fixed monthly or annual pricing.
- The real formal payment page, price, and service cycle should follow the target tenant registration page itself.
- If you are already an enterprise customer, direct discussion around delivery and deployment boundaries is usually more appropriate than the standard monthly path.
Benefit Matrix
What the free path, local script-slot expansion, monthly membership, and annual membership each give you
| Path | Best for | What you get | Current boundary |
|---|---|---|---|
| Personal free edition | Individual explorers and automation enthusiasts | Start from the public entry and the valid menu set in the personal free path, plus the CLI guide, to feel the value | Default script slots are limited and the space is not meant to be a formal team collaboration workspace |
| Local script-slot expansion | People already continuing to connect scripts in personal space | Expand local script slots inside the same personal space and get immediate quota write-back after payment | This is a one-time slot expansion, not a complete subscription center |
| Monthly team edition | Teams that want one month of formal collaboration validation first | Move into the formal standard-SaaS tenant entry and begin formal multi-user collaboration with a more stable tenant path | Final pricing and payment flow follow the target tenant page |
| Annual team edition | Teams already certain about long-term usage | Get a more stable formal tenant cycle and reduce repeated monthly renewal operations | It is still not the default path for private deployment; deeper boundary needs should be discussed directly |
Current Boundary
How the payment line should be described publicly today
- It is accurate to say that local script-slot payment in the personal free edition has completed its smallest closed loop, and the
publicsuper-admin order lifecycle has also completed its smallest closed loop. - It is accurate to say that the free path already exposes monthly and annual team-edition registration entries and clearly routes users into the formal standard-SaaS tenant entry.
- It is not accurate to say that the whole system already has a complete general self-service subscription center.
- It is not accurate to say that all payments are already connected to formal third-party gateways.
- It is not accurate to say that the free path has already closed the full registration, payment, activation, and renewal loop for formal team tenants internally.
- The more accurate public framing is this: the first version of the personal billing center plus the formal-tenant registration upgrade path already exists, while the complete general billing center is still being converged.
Sales View
If you need to explain it externally or talk about pricing, continue to the separate sales-framing page
This page is mainly about implementation boundary, payment paths, and current reality. If you need to explain how to sell it, how to layer it, or how to quote it to customers, free-path users, or presales teammates, the separate membership and pricing page is a better next step.