Your own email, chat, and files

Move a team off a stack of monthly subscriptions and onto a server you control. I run this exact setup for myself, so the configuration you get has already been through real upgrades.

  • Mail server with spam filtering, webmail, and SPF, DKIM, and DMARC records
  • Matrix chat with the Element apps and group video calls
  • Nextcloud for files, calendars, contacts, and shared documents
  • One login for everything through single sign-on
  • Off-site backups and a written runbook you keep
  • mailcow
  • Matrix
  • Element
  • Nextcloud
  • Immich
  • Authentik

Content collaboration platform with real-time document editing

A private workspace for your team: shared documents that several people can edit at once, calendars, contacts, and file sync, all running on infrastructure you control instead of a per-seat subscription.

  • Nextcloud
  • PostgreSQL
  • Redis
  • Docker
  • Rclone

Private chat, for small teams or whole companies

Encrypted messaging and group video calls on your own domain, with the Element apps on desktop and mobile. Scales from a handful of people to an organization-wide rollout, with single sign-on so access follows your existing accounts.

  • Matrix
  • Element
  • Authentik
  • OpenID Connect

Cloud migration estimates, with the pros and cons laid out

Before anything moves, I map the current setup, price out AWS, Oracle Cloud, and self-hosted alternatives, and write up the trade-offs in cost, control, and effort so you can decide with real numbers instead of guesses.

  • AWS
  • Oracle Cloud
  • Terraform
  • Kubernetes

Automation and AI-assisted workflows

Workflows in n8n or Node-RED that connect forms, spreadsheets, databases, email, and WhatsApp, with AI models wired in to draft, summarize, classify, or route work automatically. Infrastructure is written in Terraform and APIs are described in OpenAPI, so every change can be reviewed and repeated.

  • n8n
  • Node-RED
  • WhatsApp
  • Terraform
  • OpenAPI

Websites, web apps, and design improvements

Static sites in Astro, documentation portals in Docusaurus, and WordPress when you want to edit pages yourself. Apps with logins, dashboards, or admin tools get Laravel or Django with a React front end, or Supabase when a project needs Postgres, auth, and file storage quickly.

I also take existing sites and make them faster, better organized, and better looking, using AI-assisted tooling to speed up research, copy, and layout work without skipping a human review. This site is one example: Astro builds it as static HTML and OpenResty serves it from my own server.

  • Dashboards with real-time data, filters, and saved views
  • SaaS landing pages built around one clear product screenshot
  • Multi-step onboarding and signup flows that cut drop-off
  • Pricing and paywall pages with a plan comparison that doesn't confuse people

For layout and interaction details I pull from real product references, not stock templates, so the result looks like a specific product instead of a generic AI-generated page.

  • Astro
  • Docusaurus
  • WordPress
  • Laravel
  • Django
  • React
  • Supabase
  • Tailwind CSS

Not sure which of these you need?

Describe the problem in a few lines and I'll reply with how I would approach it.