bext Cloud or a hosted
JavaScript platform?
Two tools, two jobs. Here is what bext Cloud does today, what it does not do yet, and what the leading hosted platform does better.
bext Cloud
Pick bext Cloud if…
- You build WordPress sites, PrestaShop shops or sites with a built-in CMS.
- You want a fixed price per site, with no request or bandwidth meter.
- You manage sites for clients and want them grouped by client.
- You want the option to keep your sites on your own servers, with a source-available engine.
- You want an interface in French as well as English.
Leading hosted platform
Stay on the hosted platform if…
- You mostly deploy Next.js or JavaScript apps that rely on serverless and edge functions.
- Your team lives on branch previews and a deploy for every push.
- You need logs, metrics and alerts built into the platform.
- You want a global delivery network out of the box.
The details,
without rounding the corners.
The badge in the bext Cloud column shows what is open today to every account.
| Area | bext Cloud | Leading hosted platform |
|---|---|---|
| WordPress sites | Available Created in about a minute, live install progress, plugins, themes, updates, maintenance and backups from the dashboard. | No WordPress hosting: the platform is aimed at JavaScript applications. |
| PrestaShop shops | Available PrestaShop 9 or 8, a secure back office from the start, module management, maintenance with allowed IPs, a plain-language security check. | No PHP hosting and no PrestaShop shops. |
| Built-in CMS | Available Native Bext CMS for PRISM sites: pages, posts, media library, custom content types and fields. | No built-in CMS: you connect an external CMS to your app. |
| JavaScript apps | Partly TypeScript PRISM sites served by the bext engine. Deploying other apps from a repository is in internal testing. | Its core strength: Next.js and the main JavaScript frameworks, built and deployed automatically. |
| Git deploys and previews | Partly Deploy on every push and rollback to a kept release, in internal testing. No preview per branch. | Every push is built and deployed, with a preview per branch and instant rollback. |
| Staging and go-live | Available An HTTPS staging address hidden from search engines, domain ownership proved by DNS, checks before the switch and a database backup (WordPress, PrestaShop). | A preview URL per deployment, then a custom domain attached to the project. |
| Pricing | Available A fixed price per site by type, with no usage meter. A first site for free, then online payment by card. | A subscription per team member, plus usage billed beyond the included quotas. |
| Your own servers | Partly Connect a bext server you run and check that it responds. Importing the sites it serves is in internal testing. | Managed cloud only: you cannot attach your own servers. |
| Lock-in | Available The bext engine is source-available (BSL 1.1). You can install it on your own servers and keep your sites there. | The platform is closed. Some features (caching, images, edge storage) have no direct equivalent elsewhere. |
| Execution model | Available Your sites run on a server, with no per-invocation function billing. | Serverless functions billed by usage, which scale without any work on your side. |
| Observability | Partly Checks every 5 minutes with an email alert (option), on-demand checks and the shop security check. No searchable logs or metrics yet. | Built-in logs, audience analytics and performance monitoring. |
| Delivery network | Not yet No global CDN: your sites are served from the server they run on. | Global edge network included, with caching and image optimisation. |
| Agencies and tooling | Available Projects grouped by client, French and English interface, CLI and the ShellDeck desktop app. | Teams and roles, CLI and integrations with the main Git hosts. |
Performance figures for the bext engine and their methodology live on bext.dev/benchmarks.
When not
to switch.
We’re not for everyone. Stay where you are if any of these are true.
Your workflow relies on branch previews. bext Cloud has none, and its Git deploys are not open to everyone yet.
You need searchable logs, metrics, traces or alerts built into the platform.
You need a managed CDN with hundreds of points of presence out of the box.
Your apps depend on serverless or edge functions specific to the platform.
See it on your own site.
Create a WordPress site, a PrestaShop shop or a PRISM site in about a minute. Your first site is free.