P Persmon Cloud
Roadmap

What to add next, and why

Every tool here is open source, runs as one Coolify resource, and earns its place by removing a paid subscription or a manual step from how Persmon Technologies actually works: client delivery and invoicing, the websites we host for clients, data and AI work, and running the platform itself.

Nowready to deploy this monthNextafter the Now set is settledLaterwhen a client or project needs it
Capacity

Will it fit?

RAM budget if everything marked Now is added

Used today ≈ 4 GBPlanned (Now) ≈ 3.3 GBFree ≈ 7.7 GB

The five Now tools together need roughly 3.3 GB. Ollama is the only item that changes the picture — run it only when you are using it. Disk is not a constraint (157 GB free).

Priority

Now

Documenso

Now
≈ 0.5 GB RAM · Client delivery

E-signatures for client agreements, contracts and proformas (PSM-2026 series) instead of print-sign-scan. Keeps the signed copy on Persmon's own disk.

project site ↗self-hosted · open source

Invoice Ninja

Now
≈ 0.6 GB RAM · Client delivery

Invoices, proformas and quotes with the PSM numbering, Net-14 terms and ABSA details built in; recurring support billing (e.g. the TMS UGX 80k/month) and payment reminders on schedule.

project site ↗self-hosted · open source

Umami

Now
≈ 0.3 GB RAM · Client websites

Privacy-friendly analytics for the sites Persmon hosts and builds — Terrazzo Masters, Aluminium Plus, Namirembe Guest House, Bakerm — without cookie banners. One instance, one dashboard per client.

project site ↗self-hosted · open source

Metabase

Now
≈ 1.2 GB RAM · Data & AI

BI dashboards straight on Postgres/Supabase: HMS occupancy and POS revenue for Ishasha, Pearl Insights census slices, backup-size trends. Shareable read-only dashboards for clients.

project site ↗self-hosted · open source

Authentik

Now
≈ 0.7 GB RAM · Platform

Single sign-on in front of the tools (n8n, Dozzle, Beszel, Metabase…) so there is one login, MFA, and one place to revoke access when a collaborator leaves.

project site ↗self-hosted · open source
Priority

Next

Plane

Next
≈ 1.0 GB RAM · Client delivery

Project tracking for multi-phase work like the CCHCL ICT contract (three phases) and Nabugabo — issues, cycles, client-visible progress — replacing spreadsheets and chat threads.

project site ↗self-hosted · open source

Docmost

Next
≈ 0.4 GB RAM · Persmon ops

Team wiki for runbooks, SOPs, onboarding and client hand-over docs. This site explains the server; Docmost is where the how-we-work knowledge goes.

project site ↗self-hosted · open source

Cal.com

Next
≈ 0.6 GB RAM · Client delivery

Booking page for consultations and site visits, synced to Google Calendar. Clients pick a slot; no back-and-forth.

project site ↗self-hosted · open source

Formbricks

Next
≈ 0.5 GB RAM · Client websites

Client intake forms, post-project feedback surveys and lead capture for the client sites, with results in one place.

project site ↗self-hosted · open source

NocoDB

Next
≈ 0.4 GB RAM · Data & AI

A spreadsheet-style interface over Postgres tables — lets a hotel manager or a client edit reference data safely without touching the app.

project site ↗self-hosted · open source

Ollama + Open WebUI

Next
≈ 3–6 GB RAM · Data & AI

Private LLM endpoint for experiments like the Pearl AI assistant and document pipelines. 16 GB RAM fits 7–8B models; keep it stopped when not in use.

project site ↗self-hosted · open source

Stirling-PDF

Next
≈ 0.6 GB RAM · Persmon ops

Merge, stamp, compress and sign PDFs — for BOQs, proposals and contract packs coming out of the docx pipeline.

project site ↗self-hosted · open source
Priority

Later

Listmonk

Later
≈ 0.2 GB RAM · Client websites

Newsletters and campaign email for clients' marketing (guest houses, bookshop) at near-zero cost per send.

project site ↗self-hosted · open source

Chatwoot

Later
≈ 1.5 GB RAM · Client websites

Shared support inbox and website chat widget for hosted client sites; WhatsApp and email in one queue.

project site ↗self-hosted · open source

Postiz

Later
≈ 0.8 GB RAM · Client websites

Schedule social posts for client accounts from one place.

project site ↗self-hosted · open source

JupyterLab

Later
≈ 0.5 GB RAM · Data & AI

Python/R notebooks next to the data for census analysis and modelling work, without shipping CSVs around.

project site ↗self-hosted · open source

CrowdSec

Later
≈ 0.3 GB RAM · Platform

Crowd-sourced IP reputation on top of fail2ban; blocks known bad actors before they reach Traefik.

project site ↗self-hosted · open source

Backrest

Later
≈ 0.2 GB RAM · Platform

Web UI over restic for encrypted, deduplicated off-site backups (to the PC or Hostinger storage) with restore-by-click — the next step after the current tar + checksum scripts.

project site ↗self-hosted · open source
Products

Queued for this server

Not tools — Persmon's own products that will become Coolify resources here.

Method

How a tool gets added

  1. Pick it from Coolify’s one-click servicesAlmost everything above is in Coolify’s service catalogue; the rest are a Docker Compose paste.
  2. Give it a subdomain<name>.persmon.cloud — DNS already wildcards to the server, Traefik issues the certificate on first request.
  3. Put it behind Authentik once that existsOne login for every internal tool; client-facing tools keep their own accounts.
  4. Add it to the backup script and Uptime KumaNo tool is finished until its data is in the 03:00 archive and its URL is monitored.
  5. Document it hereAdd a card on the Tools page: what it is for, how it runs, where its data lives.
Live status Coolify