DeltaChat FAQ
Common questions about DeltaChat, including self-hosting, ownership, setup, domains, and how the product is intended to be used.
Quick summary
The short version of what DeltaChat is and how it is used.
Private by default
DeltaChat is designed for people who want to run a private chat space on infrastructure they control.
Self-hosted today
The current public path is the installable self-hosted product, deployed with Docker Compose.
Control without lock-in
You keep ownership of your deployment, your settings, your domain, and your data.
Best starting points
If you are evaluating DeltaChat for the first time, this is the cleanest path:
1. Read the product page
Understand what DeltaChat is, who it is for, and why it exists.
2. Follow the install guide
Use the Docker Compose deployment path to bring the stack up.
3. Browse the docs
Review configuration, troubleshooting, and upgrade guidance.
Frequently asked questions
These answers are intended to reduce friction for people evaluating, installing, or operating DeltaChat.
What is DeltaChat?
DeltaChat is a self-hostable chat server designed for private communication across family, friends, teams, and communities. It is intended to give operators a practical way to run chat on infrastructure they control.
Is DeltaChat free?
Yes. DeltaChat is currently positioned as a free installable product. You can deploy it yourself using the public repository, Docker Compose files, and documentation.
Is DeltaChat cloud-hosted by TheDeltaCore?
Not at this stage. The current public offering is the self-hosted installable product. A hosted version may come later, but the installable version is the current focus.
Who is DeltaChat for?
DeltaChat is suitable for families, friends, teams, clubs, communities, and privacy-minded groups who want a private chat space without relying entirely on a third-party platform.
Do I need to self-host it?
Yes, today the product is intended to be self-hosted. That means you run the stack on infrastructure you control, typically using Docker Compose on a Linux host.
Do I need Docker to install DeltaChat?
The current documented deployment path is Docker Compose based. That is the install model reflected in the repository and supporting documentation.
What kind of server do I need?
A Linux server is the intended starting point, with Ubuntu being a sensible default. You should have SSH access, Docker Engine, the Docker Compose plugin, and enough control over the environment to manage runtime configuration and networking.
Can I run DeltaChat locally first?
Yes. A local-first install is a sensible way to validate the stack before exposing it publicly. For public use, you should move to a real domain, HTTPS, strong secrets, and production-aware networking.
Do I need a domain name?
For production, yes. A real domain is strongly recommended so the platform can be published cleanly behind a reverse proxy with HTTPS. Localhost-style access is more suitable for first setup and testing.
Does DeltaChat support custom domains?
Yes. The operational model assumes you can run the service under hostnames you control, typically through a reverse proxy such as Nginx Proxy Manager or an equivalent setup.
Who owns the data?
In the self-hosted model, the operator owns and controls the infrastructure, runtime configuration, and stored data. That is one of the core reasons to use a self-hosted product like DeltaChat.
Are there ads or platform lock-in?
No. DeltaChat is positioned around control and ownership, not ad-supported usage or forced dependence on a third-party hosted chat platform.
Is the GitHub repo the full DeltaChat application source?
Not exactly. The public repository is currently a deployment and operations repo. It provides the Docker Compose deployment model, configuration shape, install guidance, and operational docs rather than presenting itself as the full app source tree.
What is .env.runtime?
It is the runtime environment file used to configure a DeltaChat deployment. The current deployment model expects you to copy the example environment file, review the values, secure it properly, and then start the stack using that file explicitly.
What should I secure before going live?
At minimum, review database passwords, the JWT signing key, public base URLs, reverse proxy settings, and file permissions for your runtime environment file. HTTPS and strong secrets are essential for real deployment.
What if something goes wrong during install?
The intended troubleshooting flow is to inspect container state with Docker Compose, review logs, verify environment values, and confirm connectivity between services such as the API and Postgres.
Can I upgrade DeltaChat later?
Yes. The repository documents a standard Compose-style upgrade path where you pull newer images, recreate the stack carefully, review logs, and verify that core functionality still works after the update.
Is DeltaChat meant only for businesses?
No. It is intentionally broader than that. It is suitable for personal, family, community, and team use — the key idea is private chat you can run yourself.
Quick links
Move between the main product page, the install guide, and the docs without losing context.
Ready to install DeltaChat?
Follow the installation path to bring the stack up using Docker Compose and a runtime environment file.