Websites
The Apps Catalogue
The Apps catalogue is a browsable library of web applications you can put on a site you already host with Kapsule, from WordPress and WooCommerce to wikis, analytics, file sync and automation tools.
What the Catalogue Is
Apps are software that runs on your hosting, not extra products you subscribe to. You already pay for the site; an app is what you choose to run on it.
The catalogue exists so you do not have to research, download, unpack and configure that software yourself. Most entries carry a proven installer that sets the app up on a site you nominate, creates its database, generates an admin account, and hands you the login.
Apps is a top-level item in the KPanel sidebar, between Domains and the server sections. The direct address is /apps.
What Apps Cost
Nothing. Apps are installed onto a site you already pay for, so there is no charge for the app itself and nothing to refund. What you pay for is the hosting underneath it.
That has one practical consequence worth planning around: a heavier app uses more of your plan's resources. A wiki for five people and a busy store are very different loads on the same plan.
Browsing and Searching
The catalogue page opens with a count pill showing how many apps are currently in the catalogue, a search box, and a row of category chips.
- Search matches on the app name, its slug and its tagline. Typing filters the whole catalogue into one flat grid of matches.
- Category chips filter by type. They are multi-select: click several to widen the filter, click All to reset.
With no search and no chip selected, the page shows a single featured app in a wide hero card, then the rest grouped into labelled category sections so a large catalogue stays browsable.
The categories are: CMS, eCommerce, Analytics, Files, Wiki, Forums, Email, Automation, Headless CMS, Project Mgmt, CRM, DevOps, Education, Static Sites, and Tools.
If you know roughly what you want but not what it is called, use the category chips rather than search. "Wiki" and "Headless CMS" surface options most people would never think to search for by name.
Reading a Tile
Every tile in the gallery carries the app's icon, its name, a one-line tagline, and one or two pills:
- A runtime pill:
PHP,NODEJS,STATICorPYTHON. This is what the app is built on, and it tells you what kind of hosting environment it needs. - A Community pill, on apps whose installer is community-contributed. The install script is included but may need a few manual steps to finish setup.
Reading an App Page
Click any app to open its detail page. It has two halves.
The left column tells the story:
- The app icon, name and tagline, with pills for its runtime, its category, whether it requires a database, whether it is Community, and whether it is Featured.
- About [app]: what the software actually does.
- At a glance: resource facts, plus outbound links to the project's own documentation and homepage.
The At a glance cards can include:
| Fact | What it tells you |
|---|---|
| Install time | Roughly how long the install takes |
| Min RAM | The memory the app needs to run |
| Min disk | The disk space it needs |
| Database | Whether one is auto-provisioned for you |
The right column is a sticky install panel with the Install [app] button and any notes that apply to that app.
Installable Apps and Apps We Set Up by Hand
Every app in the catalogue is orderable. There is no "coming soon" dead end. What differs is how it gets installed:
- Apps with a proven installer are provisioned automatically. You configure it, confirm, and watch a progress bar.
- Apps without a proven installer are installed by our team by hand. The app page says so: Set up by our team: we install this app by hand after you order and email you when it is live. You still click the same button, and you still pay nothing.
The reason for the split is deliberate: running an unverified install script against a customer's live site is a good way to break it. Where we cannot guarantee the script, a person does the work.
Community Apps
An app marked Community has an install script contributed rather than maintained in-house. The app page is explicit: the install script is included and may need a few manual steps to finish setup.
Treat a community app as "installed, not configured". The software will be on your site and reachable, but expect to do the final setup wizard yourself, and check the project's own documentation for anything the installer could not do. Take a backup before you start. See Taking a Backup.
Recommended Plan Levels
Some apps note a recommended minimum plan level on their page, and the install wizard shows a Plan upgrade recommended notice when your current plan is below it.
That notice is advice, not a block. The install proceeds either way. What it is warning you about is real, though: an app that wants more memory than your plan comfortably gives it will either fail during install or run badly afterwards. Check the Min RAM figure on the app page against what your plan provides before you ignore it.
Who Can Install
Installing requires the apps:write permission, held by account Owners and Admins. Other roles can browse the whole catalogue and read every app page, but the install button is locked with a note about which roles can act.
What If It Fails
The catalogue will not load. The page shows an error card with a Try again button. This is a load failure, not an empty catalogue.
"No apps match your search." Clear the search box or click the All chip to reset the category filter. Multi-select chips are easy to leave switched on by accident.
An app you expected is not there. The catalogue is curated. If something you need is missing, open a support ticket and ask: adding an app to the catalogue is a normal request, not an unusual one.
The app page shows an error. Go back to All Apps and try again from the tile. If it persists for one specific app, report the app slug in a ticket.
Next Steps
Once you have picked an app, Installing an App on Your Site walks through the wizard end to end, including what happens when the target site is not empty.