카탈로그
Every catalog entry declares the resources it needs. On install, the platform creates them and connects them: database, object storage, mail, domain, TLS and sign-in.
Available now
Grouped by what you are setting up. Take a whole group, or just the entries you need.
| Group | Entries |
|---|---|
| Solo developer | PostgreSQL · SeaweedFS · Valkey · Gitea |
| Small development team | PostgreSQL · SeaweedFS · Valkey · Gitea · kube-prometheus-stack · Uptime Kuma · Rocket.Chat · Docmost |
| Running a business | PostgreSQL · Valkey · Odoo · Nextcloud |
What each one is
- PostgreSQL — Relational database. Most applications ask for one.
- Valkey — Redis-compatible in-memory store, for caches and job queues.
- SeaweedFS — S3-compatible object storage. Files, attachments, backup targets.
- Gitea — Git repositories and issues. Replaces GitHub.
- kube-prometheus-stack — Metrics collection with Grafana dashboards and alerts.
- Uptime Kuma — Watches whether your services are up, and tells you when they are not.
- Rocket.Chat — Team chat. Replaces Slack.
- Docmost — Wiki and collaborative documents. Replaces Confluence or Notion.
- Odoo — ERP and CRM. Accounting, inventory and sales in one place.
- Nextcloud — File sharing and sync. Replaces Dropbox or Google Drive.
Connections and usability under review
Not installable yet. Each entry appears in the catalog once its connections are defined and its behaviour on the platform has been checked. The "Needs" column is the work that falls to you on other platforms.
| App | Replaces | Needs |
|---|---|---|
| Twenty | Salesforce, HubSpot | PostgreSQL · Valkey · S3 |
| Documenso | DocuSign | PostgreSQL · S3 · SMTP |
| Chatwoot | Intercom, Zendesk | PostgreSQL · Valkey · S3 · SMTP |
| Plausible | Google Analytics | PostgreSQL · ClickHouse · SMTP |
| Langfuse | LangSmith | PostgreSQL · ClickHouse · S3 · Valkey |
Four of the five need S3-compatible storage. SeaweedFS is a catalog entry too, so the storage is installed on your own hardware and connected to the app. There is no external bucket to arrange first.
Twenty — CRM
An open source CRM. Contacts, companies, deals and a customisable pipeline, with a keyboard-driven interface.
Self-hosting matters here because a CRM holds your customer list. Seat pricing is what makes commercial CRMs expensive; on your own server the number of users is your decision.
Documenso — electronic signatures
Send documents for signature and store the signed originals.
Signed contracts are legal records. On a hosted service they live on someone else's server, and the free tier caps how many you can send each month. Self-hosted, the volume is unlimited and the originals stay with you.
Chatwoot — customer support
A shared inbox for email, website chat and messaging channels, with team assignment and canned replies.
Support conversations contain customer data, often personal. Keeping them on your own server removes the question of where that data is processed. Agent seats are not billed.
Plausible — web analytics
Lightweight, privacy-focused site analytics. No cookie banner required.
Self-hosting means visitor data never reaches a third party, which is the point of choosing Plausible in the first place. Historical data has no retention limit.
Langfuse — LLM observability
Traces, prompts, evaluations and cost tracking for applications built on language models.
Traces contain your prompts and your users' inputs. Sending them to a hosted service means sending exactly the data you were careful about. Self-hosted, they stay in your cluster next to the model.
What tidoly does with them
Installing the app is the short part; connecting it is the long part. tidoly does the connecting: the database is created and its credentials injected, storage and mail are wired, the domain gets ingress and a renewing certificate, and sign-in is configured against your existing accounts.