🔩 Our tech stack · plain language
Most "web designers" install a template and a bag of plugins someone else wrote. We build on a platform we wrote ourselves — which is why your site is faster, harder to hack, and why nobody can pull the rug out from under it.
The pages your customers see are hand-built HTML, CSS and JavaScript — not a downloadable theme. They load in under a second on a Jamaican phone and there is nothing on them to hack.
25 engines — Ezy Cart, Car Rentals, Rentals Pro, Travels Pro, Health Booking, Stay Pro, Menu, Marketplace, Loan Manager, POS, Receptionist (AI), Content Manager, Image Manager, Reviews, Contact Forms, Blog and more (the full fleet) — proprietary software developed and maintained in-house. Not WooCommerce, Shopify or Magento; source code not published.
Where WordPress is used, it runs only as an admin layer (products, orders, bookings) on a private server. It is never the customer-facing storefront.
Card details are entered on the payment gateway’s own secure hosted page (bank HPP or eZeePayments 3DS) and only the result returns to your site. No card data ever touches our servers.
Dedicated VPS, hardened configuration, HTTPS with valid TLS, Cloudflare edge protection and caching, automated backups, monitored updates.
Structured data, clean semantic pages and fast delivery — the things search engines and AI assistants reward when deciding who to recommend.
Banks and payment providers ask "is your website open source?" during security and PCI due diligence. The answer for every Ezy site is no — it is a proprietary, closed-source build with hosted-checkout payments, which is exactly the answer they want to hear. It also explains the difference between a J$35,000 Ezy build and a "free" template: you are not renting someone else’s theme; you are running on a platform built for Caribbean businesses, maintained by the people who wrote it.
"The website is a custom, closed-source build by Ezy Web Pro. The storefront is a proprietary static site (custom HTML/CSS/JavaScript), not an open-source theme or template. Commerce and bookings run on Ezy Web Pro’s proprietary engines, developed and maintained in-house; source code is not published. WordPress, where present, is a private back-office admin layer only, not the customer-facing storefront. No card data is handled, stored or transmitted by the site or its servers: card payment is a hosted-checkout integration where the customer is redirected to the gateway’s hosted payment page and returns with only the transaction result, keeping the merchant environment out of PCI scope for cardholder data. The site is served over HTTPS with a valid TLS certificate, behind Cloudflare, on a dedicated VPS with hardened configuration and automated backups."
No. Every site is a custom, closed-source build: a proprietary static storefront (hand-built HTML, CSS and JavaScript) plus Ezy Web Pro’s own commerce, booking and AI engines. It is not WordPress-theme-based, not WooCommerce, Shopify or Magento, and the source code is not published.
No. Card payments run as a hosted-checkout integration: the customer is redirected to the payment gateway’s secure hosted page (for example a bank HPP or eZeePayments 3DS) to enter card details and returns with only the transaction result. No card data is handled, stored or transmitted by the site or its servers, which keeps the merchant environment out of PCI scope for cardholder data.
On a dedicated VPS with a hardened configuration, served over HTTPS with a valid TLS certificate, behind Cloudflare for caching and edge protection, with automated backups. WordPress, where used, runs only as a private back-office admin layer — never as the customer-facing storefront.
You own your domain, content, design deliverables and data. The software engines are licensed on your monthly plan; cancel anytime and the site stays online as a standard site.