One-click applications that finish the job.
Pick one and we do the rest: create and name the database, issue the certificate, generate an admin password inside your own browser. If a step fails, the whole install rolls back.
58 in the catalogue·43 install in one click·15 categories
Declared steps
site-createdatabase-createwp-clishellset-languagessl-issue
Live gate
- Waiting for the install to finish.
3 consecutive 200s carrying that marker, 3 seconds apart. A 502, an error page or a missing marker resets the streak to zero.
Ready. Nothing has been changed yet.
Showing 58 of 58 applications.
Every application here is included with every hosting plan. The time on a card is that installer's own measured duration, and the cards without one are the ones an engineer sets up for you.
A declared sequence, and a gate that has to agree
The installer is not a copy of files into a folder. It checks the web root is empty, creates and names the database, selects the runtime, writes the configuration, issues the certificate, and then re-fetches your real public address over HTTPS and requires three consecutive answers carrying the expected content before it will call the install live.
If the web root already has something in it the installer refuses, says so, and takes a full backup before it will overwrite anything.
Fifteen of the fifty-eight, an engineer installs
Some need a vendor licence key that belongs to you and not to us. Some want a container runtime we will not run next to other customers on a shared machine. Ordering them works exactly the same way: the request is recorded the moment you place it, an engineer sets it up, and you are told when it is live. We would rather name them than quietly fold them into a headline number.
The things worth asking first
Does an application cost extra?
No. The catalogue comes with hosting. What an application costs you is the resources it uses on the plan you already have, which is why each card names its minimum memory.
Can I install more than one?
Yes, one per site. A plan that carries ten sites can carry ten applications, and each gets its own database where it needs one.
What happens to the site that is already there?
Nothing, unless you say so. If the web root is not empty the installer stops and tells you. If you choose to continue anyway it takes a full backup of what is there first.
Do you keep the application updated afterwards?
WordPress, yes: core, plugins and themes update themselves with a backup taken first and an automatic rollback if the site stops answering. For everything else you update from the application's own admin, as you would anywhere.
Which applications need a database?
Each card says. Where one is needed the installer creates it, names it and wires the credentials in. You never handle a connection string.
What if the install fails halfway?
It rolls back and the site is left as it was. The panel names the phase that failed in plain words, and the full technical detail goes to support automatically, so you never have to describe what happened.
The plan first, then the application.
Every hosting plan carries the whole catalogue. Start on the smallest one and install what you came for.