166 gotowych aplikacji. Każda na jedno kliknięcie.

1. Hosting for a single website is a different challenge from hosting a whole suite of tools.

You rarely need just one website these days. Besides a landing page or online store, you'll usually want a CRM for customer contacts, an automation tool for repetitive tasks, a database for internal tables, and maybe a live chat widget for customer support. Buying separate hosting for each tool quickly becomes uneconomical and hard to manage.

On Saplo, all these tools are simply apps in one catalog, installed on the same Box as your business site: the no-code Baserow database, Chatwoot for chat, n8n for automation, a ticketing system, or an admin panel. Each one runs as a separate, isolated app in its own LXC container.

The catalog includes 166 ready-made apps, most of them complete installation recipes rather than just tech stacks like Node or Django. These include Nextcloud, Gitea, Grafana, Metabase, Uptime Kuma, Paperless-ngx, Vaultwarden, and many other business tools.

2. How are resources counted when you install multiple apps on one Box?

The number of apps and domains is unlimited on every plan, but the real constraint is the Box's RAM, because every app declares a minimum memory requirement in its manifest, such as 256 MB for a simple WordPress site, 1 GB for n8n, and 2 GB for apps based on a full Docker stack, such as Baserow or Chatwoot.

Box M (2 GB RAM) can realistically run one resource-heavy Docker app alongside a lighter website. Box L (6 GB RAM) can run several Docker apps at once, while Box XL (12 GB RAM) comfortably handles a full suite of business tools on one account, with no need to decide which apps to disable.

You can add RAM and vCPU without migrating (hot-add). As your toolkit grows, you do not need to move everything to a new server, just increase the resource limit for the same Box.

3. Why this is different from traditional hosting

Traditional shared hosting is designed for a single website per account, with a limited number of databases and PHP processes. Installing multiple independent apps on it, such as a CRM, a chat app, or automation tools, usually exceeds what the panel and its limits were designed to support.

A VPS lets you run any number of apps, but you must install, configure, and secure each one yourself. For a set of several different tools, each with its own dependencies, database, and ports, this means real administrative work at setup and after every update.

Saplo combines both approaches: the flexibility of a VPS (multiple independent apps and full SSH access from Box M upwards) with the convenience of panel-based hosting (a ready-made installation recipe for each of 166 apps, automatic SSL, and preconfigured LXC isolation).

4. Example stack for a small business

A WordPress company website, Baserow as an internal customer and order database, Chatwoot for customer chat on your site, and Uptime Kuma for monitoring are four different apps that fit on a single Box L, without four separate bills from four different providers.

Adding a fifth app, such as n8n for automating notifications between your other tools, is just another installation from the catalog, not another hosting agreement or a migration of existing data to a different server.

5. Who it is for

For a small business looking to replace several paid SaaS subscriptions (CRM, chat, automation) with self-hosted installations on a single Box, this can be cheaper over a year than paying for each subscription separately, especially as the number of SaaS tools grows.

For a technical team that prefers to retain control of its own data through self-hosting rather than store it in third-party SaaS services, where customer and company data lives on someone else's servers.

If you are just testing which tools you need, the catalog of 166 apps lets you experiment without the financial risk of a separate agreement for every tool you test.

6. How to choose the first apps to deploy on your Box

Start with your company website (WordPress or a simple static site), as it is usually the first point of contact with customers and a natural starting point for every new Box, regardless of your plans for expanding the toolset.

Add a tool that genuinely replaces a paid SaaS subscription, such as Baserow instead of a spreadsheet shared by email, or Chatwoot instead of a third-party website chat tool with a monthly per-user fee.

Monitor RAM usage in the dashboard after each app you add, so you know when to add resources using the hot-add option instead of discovering the limit at the worst possible time, during an out-of-memory failure.

Test new tools on the same Box without the financial risk of a separate agreement. Installing and removing an app from the catalog carries no extra charge beyond the resources it uses while running.

Document what each app is used for across the team. With several tools on one Box (CRM, chat, automation, monitoring), it is easy to forget which are actively used and which should be removed to free up resources.

7. Self-hosted vs. SaaS: what really matters in the cost calculation

SaaS costs usually grow with the number of users or monthly operations, which means a growing team faces a steadily rising bill, even if the tool itself does not change.

The cost of self-hosting on Saplo is fixed (the price of the Box), regardless of how many users use the installed apps. For a growing team, this makes costs predictable and easier to plan for in the annual budget.

On the other hand, self-hosting means you have to update the apps yourself (new versions of Baserow, Chatwoot, and others), although the Saplo engine makes this easier with ready-made update recipes in the catalog.

Self-hosted data stays physically in your container, which can be an important consideration for companies processing customer personal data through internal tools such as CRM and chat when assessing GDPR compliance compared with an external SaaS.

8. Security with multiple apps on one account

Running several apps on one Box (CRM, chat, automation, monitoring) creates several potential attack targets, so LXC container isolation is more important here than it is for a single, simple site.

Each app on Saplo has its own container with its own file system, process, and (if needed) database. This means that compromising one app (for example, through an outdated WordPress plugin) does not automatically grant access to other apps on the same Box.

Security updates for individual apps (new versions of Docker images for Baserow, Chatwoot, and others) are available as update recipes in the catalog, making it easier to keep multiple different engines up to date without having to track each open source project separately.

Keep passwords and API keys separate for each app (for example, a Chatwoot token and an n8n webhook key), and do not reuse the same password across tools. If one password is compromised, every app that shares that secret is at risk.

SSH access with sudo across the entire Box (starting with Box M) grants administrative access to every container on it. If multiple people on a team access the same Box, carefully manage who actually needs server-wide access.

Regularly reviewing the list of installed apps (whether they are all still actively used) is a security best practice. A forgotten, outdated app that no one uses is a weak point that is easy to overlook as the catalog of tools on the Box grows.

9. How the app catalog grows and where new recipes come from

Saplo's app catalog is not a closed, static list. A nightly agent regularly adds new installation recipes, so the number of available apps grows over time. If you use Saplo today, you may find a tool in the catalog a few months from now that was not available when you bought your Box.

Every new recipe passes a test gate before entering the customer-facing catalog. This helps ensure the installation actually works before you try it on your production Box, not just in the agent's test environment.

Customers can suggest adding specific apps to the catalog if they need a tool that is not yet available. This sets Saplo apart from closed platforms, where the provider fully controls the list of available apps and users have no way to influence it.

An expanding catalog also makes it worth reviewing the list of available apps from time to time, even if your current toolkit fully meets your needs. A new recipe might replace a paid SaaS subscription your company uses elsewhere.

For companies tracking the evolution of their tech stack, this catalog flexibility is a real advantage over providers with a limited, rarely updated list of ready-made apps, because you do not have to wait months for a new tool to be added to the offering.

10. Keeping the tool catalog organized as it grows

As the number of applications on a single Box grows, it becomes easy to lose track of what each one does, especially when ownership of individual tools changes within the team. That is why it is worth keeping a simple list from the start: application name, purpose, and the person responsible for it.

Regularly reviewing installed applications, for example once a quarter, helps identify those that are no longer actively used but still consume the Box's RAM. This frees up resources without requiring an upgrade solely because of forgotten, unused installations. The same review is a good opportunity to check whether updates available in the catalog have been applied to every installed application, not just those used most often in the team's daily work.

Technical teams should also document which applications are connected to each other, such as an n8n automation linking chat with a CRM. Removing one connected application without checking its dependencies first may silently break another related automation.

Keeping the app catalog on your Box organized becomes more important as more people in your company gain access. Without clear documentation, a new team member may not know which tools are critical to your operations and which can be safely removed.

11. Summary: One Box as your company's tool hub

A catalog of 166 applications transforms hosting from a place for a single company website into a hub for your entire company's tools: CRM, chat, automation, monitoring, and databases, all in one account, with one invoice and one shared infrastructure to manage. For a small business, this offers a real opportunity to replace several paid SaaS subscriptions with self-hosted installations, while keeping control of your own data and avoiding subscription fees that keep growing with every new tool added to your tech stack.