System status
A simple public status page for launch readiness and supported conversion engines.
Operational after the production server is deployed and HTTPS is enabled.
Ready for WooCommerce and Stripe/PayPal production credentials.
Ready when the Windows worker has activated Illustrator and a live API token.
Ready on servers where Ghostscript and Inkscape are installed.
Planned. These require their licensed desktop applications on controlled workers.
Contact, feedback, and community pages are connected to the support workflow.
Web app
WordPress front end, account pages, localized URLs, REST API, sitemap, and clean public routes are ready for deployment.
Payments
Checkout flow is ready for live gateway keys and webhooks. No card data is stored by VersionFixer.
Workers
AI, PDF/SVG, PSD, InDesign and 3D worker hooks exist. CAD, CorelDRAW, BIM, mechanical, and video workers still require production machines.
Support
Contact, feedback and community pages are connected to the support workflow.
Launch FAQ
Where do I check worker readiness?
Administrators can open VersionFixer > Conversion Jobs or the /wp-json/versionfixer/v1/workers endpoint.
Can customers see failures clearly?
Yes. The frontend shows readable queued, processing, completed, and failed states, and account history keeps job notes.
Can status be automated later?
Yes. A dedicated uptime/status provider can be linked when traffic grows.