Layer 5 · self-hosting reality check
What it actually takes to self-host Appointments for Nextcloud
The docs say Nothing of its own, because it's a Nextcloud app. Nextcloud's minimum is 128 MB RAM per PHP process, with 512 MB per process recommended. In practice you want Whatever your Nextcloud already uses, since the app adds no services. A Nextcloud stood up just for booking still means running all of Nextcloud; 4 GB is comfortable. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Calendly alternatives, where Appointments for Nextcloud is one of the picks.
Wondering whether you need to at all? Is Calendly free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | Nothing of its own, because it's a Nextcloud app. Nextcloud's minimum is 128 MB RAM per PHP process, with 512 MB per process recommended |
|---|---|
| RAM — what it really needs | Whatever your Nextcloud already uses, since the app adds no services. A Nextcloud stood up just for booking still means running all of Nextcloud; 4 GB is comfortable |
| CPU | Nextcloud's, unchanged |
| Disk | Negligible beyond Nextcloud. Bookings are saved as events in a destination calendar in your Nextcloud Calendar. |
| Monthly cost | $0 on a Nextcloud you already run; otherwise the cost of Nextcloud itself, $12–24/mo on a 4 GB VPS |
| Setup time | 15 minutes from the Nextcloud app store, plus an hour to build your schedule |
| How you install it | Apps, search Appointments, Enable. Then pick a calendar, build the weekly template, enable sharing and copy the public page link. Confirmation emails go out through Nextcloud's own mail settings, so set up SMTP there first |
| Ongoing maintenance | Check the app's supported Nextcloud versions before every major Nextcloud upgrade, because it's one developer's app and can trail Nextcloud's releases. Otherwise it updates through the app store like any other app. |
| Where it stops scaling | It scales with the Nextcloud it lives in. Booking traffic is trivial next to file sync, so the limit is your Nextcloud, not the app. |
The thing that catches people out
It lags behind Nextcloud's major releases. Nextcloud 35 shipped on 2026-09-15, and the latest Appointments release (2.7.4, June 2026) declares support only up to Nextcloud 34. Upgrade and Nextcloud won't run the app, so your public booking page goes dark. In the open issue (#690), users report force-enabling it on 35 without errors, but that's unsupported. Hold Nextcloud at 34 until an Appointments release declares 35, or force-enable it knowing the risk.
When not to self-host Appointments for Nextcloud
You don't already run Nextcloud. Standing up a whole Nextcloud for a booking page is the wrong trade, so use Easy!Appointments or Cal.diy. Also skip it if the booking page is business-critical and you can't hold back Nextcloud upgrades.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 5 self-hosting guides
- Self-hosting LibreOffice2 GB with a large spreadsheet open
- Self-hosting ONLYOFFICE6 GB for the Document Server with a handful of concurrent editors
- Self-hosting Collabora Online4 GB, and roughly 1 GB per 20 concurrent documents
- Self-hosting CryptPad2 GB for a small instance
- Self-hosting Mattermost4 GB for a team of 50 with PostgreSQL on the same box
- Self-hosting Rocket.Chat6 GB with MongoDB on the same machine
Common questions
- How much RAM does Appointments for Nextcloud actually need?
- Whatever your Nextcloud already uses, since the app adds no services. A Nextcloud stood up just for booking still means running all of Nextcloud; 4 GB is comfortable in practice. The documented minimum is Nothing of its own, because it's a Nextcloud app. Nextcloud's minimum is 128 MB RAM per PHP process, with 512 MB per process recommended, which is the figure at which the process starts rather than the figure at which it works under real use. Nextcloud's, unchanged alongside it.
- What does self-hosting Appointments for Nextcloud cost per month?
- $0 on a Nextcloud you already run; otherwise the cost of Nextcloud itself, $12–24/mo on a 4 GB VPS This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for check the app's supported Nextcloud versions before every major Nextcloud upgrade, because it's one developer's app and can trail Nextcloud's releases. Otherwise it updates through the app store like any other app.
- How long does it take to set up Appointments for Nextcloud?
- 15 minutes from the Nextcloud app store, plus an hour to build your schedule, via Apps, search Appointments, Enable. Then pick a calendar, build the weekly template, enable sharing and copy the public page link. Confirmation emails go out through Nextcloud's own mail settings, so set up SMTP there first.
- When should I NOT self-host Appointments for Nextcloud?
- You don't already run Nextcloud. Standing up a whole Nextcloud for a booking page is the wrong trade, so use Easy!Appointments or Cal.diy. Also skip it if the booking page is business-critical and you can't hold back Nextcloud upgrades.
- What is the most common mistake when self-hosting Appointments for Nextcloud?
- It lags behind Nextcloud's major releases. Nextcloud 35 shipped on 2026-09-15, and the latest Appointments release (2.7.4, June 2026) declares support only up to Nextcloud 34. Upgrade and Nextcloud won't run the app, so your public booking page goes dark. In the open issue (#690), users report force-enabling it on 35 without errors, but that's unsupported. Hold Nextcloud at 34 until an Appointments release declares 35, or force-enable it knowing the risk.