In-house · Self-hosted infrastructure · Live
Our own production stack
We run the same kind of stack we build for clients: mail, live chat and this website.
Self-hosted, custom-branded services on our own server, maintained by us and serving real traffic. Their live status is on our homepage.
- Type
- In-house infrastructure
- Host
- Ubuntu VPS
- Stack
- Docker · Apache · Let’s Encrypt · systemd
- Status
- Live, checked every 30 seconds
3
self-hosted services
1
inbox for chat and email
30s
between live status checks
The problem
A studio asking clients to trust it with their infrastructure should run its own. We wanted our mail, support chat and website on our own domain, under our own control, with nobody else’s branding on them.
What we built
Mail runs on a self-hosted mail server with webmail, custom branding and an SMTP relay for outbound deliverability.
Live chat runs on a self-hosted, custom-branded help desk, the chat bubble on this site. Emails to support@thynkdone.com land in the same inbox as chat conversations.
This website is a Next.js frontend with a FastAPI backend and a headless CMS for the blog, served by Apache with Let’s Encrypt certificates.
How it works
Mail
mail.thynkdone.com: our own mail server with webmail and relay-backed delivery.
Live chat
help.thynkdone.com: a branded help desk for chat and email in one inbox.
Website & API
thynkdone.com: Next.js, FastAPI and a headless CMS, deployed with systemd.
The stack
- Postfix · Dovecot · Webmail · SMTP relay
- Support
- Ruby on Rails help desk · PostgreSQL · Redis
- Website
- Next.js · FastAPI · Sanity CMS
- Platform
- Docker · Apache · Let’s Encrypt · systemd
Tell us what you’re working on
A senior engineer reads every message and replies within 24 hours, with questions or first thoughts.