Plan model
Free workspace
A restricted Universal By Foundation workspace for proving route value before operational rollout. Current model: 25 starter tokens each month.
Conversion workspace
This workspace should make it obvious what ran recently, what needs review, which plan is active, how many tokens are left, and where upgrade or billing requests should go.
Plan model
A restricted Universal By Foundation workspace for proving route value before operational rollout. Current model: 25 starter tokens each month.
Token summary
Free access should prove route value before upgrade.
Upgrade path
Daily reset access with 40 tokens reset every day.
Plan actions
Current plan: Free — 25 starter tokens each month
Billing portal and self-serve plan management are now configurable in the theme shell. If checkout is not configured yet, the workspace should still fall back cleanly to pricing and contact sales.
Billing support: webmaster@inkfire.co.uk
Connector availability
Hosted workspace is the baseline. WordPress, ChatGPT, and Claude follow the plan shell, while Gemini remains staged.
Continue where you left off
Use the converter to generate your first result. Once something has run, this dashboard becomes much more useful.
Dependency warnings
Recent conversions have not yet saved dependency flags. Once jobs are rerun through the current broker, this list will surface what needs review most often.
Current plan access
Commercial shell: Free: 25 starter tokens each month | Lite: 40 tokens reset every day | Pro: 1,500 tokens each month | Agency: 8,000 shared tokens each month
Commercial readiness
Stable routes are for primary use. Beta routes should stay visible as structured experiments, not hidden production guarantees.
Token activity
No token activity is recorded yet. Once credits are seeded, deducted, or granted, the latest account activity will show here for support and review.
Account API
The hosted workspace, WordPress connector, and future AI entry points can all read the same account shell through the authenticated account endpoint instead of duplicating plan and token logic in multiple clients.
/wp-json/siteport/v1/account for authenticated account state/wp-json/siteport/v1/plans for public plan catalog metadata/wp-json/siteport/v1/billing-webhook for staged billing eventsRoute updates
Recommended next step
Plan tiers
Billing rule
Universal By Foundation is infrastructure. Tokens, route coverage, storage, connectors, and protected execution all create ongoing cost and ongoing value, so the dashboard should make recurring plan logic obvious even before self-serve billing goes live.
Current plan: Free — 25 tokens / month
Free
A restricted Universal By Foundation workspace for proving route value before operational rollout.
Lite
For solo operators who need the full core route set without team overhead.
Pro
For developers and designers shipping repeatable migration work and client delivery.
Agency
For studios and agencies managing multiple users, higher-volume migrations, and rollout planning.
Recent conversions
The table should make validation state, preserved output, and review flags scannable before anyone opens a single row.
Run your first route to start building a history. You will be able to reopen outputs, review warnings, and compare results here.
Start conversionRoute health
This view should help teams see what is stable, what is beta, and where fallback-heavy routes still need closer review before production use.
| Route | Status | Best for | Docs |
|---|---|---|---|
| Elementor → Divi | Stable | Agency standardisation, inherited client sites, and migration away from builder lock-in. | View route |
| Elementor → Divi 4 Legacy | Stable | Teams using the Elementor to Divi 4 Legacy route. | View route |
| Elementor → Elementor | Stable | Validation, cleanup, and portability checks before larger migrations. | View route |
| Elementor → HTML / Code | Stable | Teams using the Elementor to HTML / Code route. | View route |
| Divi → Elementor | Stable | Inherited client sites, stack migrations, and legacy rescue work. | View route |
| Divi → HTML / Code | Stable | Teams using the Divi to HTML / Code route. | View route |
| Divi 4 Legacy → Elementor | Stable | Legacy rescue work, inherited Divi 4 sites, and shortcode-heavy migration projects. | View route |
| Divi 4 Legacy → HTML / Code | Stable | Teams using the Divi 4 Legacy to HTML / Code route. | View route |
| Code → Elementor | Stable | Landing pages, section libraries, and developer-to-marketer handoff. | View route |
| Code → Divi | Stable | Template reuse, modular landing pages, and Divi-first delivery teams. | View route |
| Code → Divi 4 Legacy | Stable | Teams using the Code to Divi 4 Legacy route. | View route |
| Figma → Divi | Beta | Experimental design-to-Divi workflows that need structure-aware output and clear limitations. | View route |
| Figma → Elementor | Beta | Experimental design-to-Elementor workflows that need structural output more than strict visual parity. | View route |
| Figma → HTML / Code | Beta | Teams using the Figma to HTML / Code route. | View route |
| Webflow → Divi | Beta | Beta workflows testing Webflow to Divi portability with review-heavy expectations. | View route |
| Webflow → Elementor | Beta | Beta workflows testing Webflow to Elementor portability with review-heavy expectations. | View route |
| Webflow → HTML / Code | Beta | Teams using the Webflow to HTML / Code route. | View route |
| Wix → Divi | Experimental | Teams using the Wix to Divi route. | View route |
| Wix → Elementor | Experimental | Teams using the Wix to Elementor route. | View route |
| Wix → HTML / Code | Experimental | Teams using the Wix to HTML / Code route. | View route |