sami7777/dashcaddy.net
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[grade=A] Add founder story to DashCaddy About

Browse Source
This commit is contained in:
Krystie committed 2026-10-05 21:03:28 -07:00
1 parent 5c71f251ca
commit df000a4d11
1 file changed
+41 -22
Download Patch File Download Diff File Expand all files Collapse all files
src/app/about/page.tsx
+41 -22
View File
@@ -23,38 +23,57 @@ export default function AboutPage() {
</div>
</section>
{/* Story */}
{/* Founder Story */}
<section className="py-20 px-4">
<div className="max-w-3xl mx-auto">
<h2 className="text-2xl font-bold text-white mb-6">Our Story</h2>
<h2 className="text-2xl font-bold text-white mb-6">
The Story Behind DashCaddy
</h2>
<div className="space-y-4 text-surface-300 leading-relaxed">
<p>
Self-hosting is powerful. You own your data, you control your
infrastructure, and you&apos;re not at the mercy of SaaS
providers who can change their terms, raise prices, or shut down
overnight. But let&apos;s be honest &mdash; it can also be a
pain.
I&apos;m Sami Ahmed, the creator of DashCaddy. I built it because
I wanted a simpler, more organized way to manage the applications
and services running on my own network.
</p>
<p>
Every new service means editing Caddyfiles, creating DNS
records, configuring SSL certificates, writing Docker Compose
files, and hoping everything plays nicely together. Multiply that
by 20, 30, or 50 services, and you&apos;ve got a full-time
operations job on your hands.
The project&apos;s roots go back to 2024. What began as a personal
dashboard gradually developed into a broader idea: adding an
application should also take care of the configuration needed to
make it accessible.
</p>
<p>
DashCaddy was built to solve this. One click to deploy an app.
SSL, DNS, and reverse proxy configuration happen automatically.
A beautiful dashboard with real-time WebSocket updates to monitor
everything. Natural language AI commands so you can just say
&ldquo;deploy Plex&rdquo; and it happens. And when something
goes wrong, you know about it immediately &mdash; not when a
family member texts you that Plex is down.
Working with my own infrastructure shaped that vision. Managing
reverse proxies, certificates, DNS records, and individual
services showed me how much repetitive work self-hosting can
involve. Choosing Caddy helped establish the foundation for the
project that became DashCaddy.
</p>
<p>
We believe self-hosting should be accessible to everyone, not
just people who enjoy writing YAML at 2 AM. DashCaddy makes it
beautiful, effortless, and intelligent.
Since then, DashCaddy has grown beyond a service directory into a
platform for deploying applications, managing connectivity,
monitoring services, and bringing everyday administration into
one interface.
</p>
<p>
AI-assisted development has been part of that journey from the
beginning. I started with ChatGPT and Claude, later incorporating
coding agents such as Hermes into my workflow. I direct the
project&apos;s design and development, using these tools to help
implement ideas, investigate issues, and improve the software.
</p>
<p>
DashCaddy continues to evolve through practical experience and
ongoing refinement. Its purpose remains the same: make
self-hosting easier to understand and manage, while keeping
people in control of their own servers.
</p>
<p>
DashCaddy&apos;s mission is to make homelabbing more accessible.
Whether you&apos;re setting up your first home server or managing
an established network, the goal is to simplify the work of
deploying and maintaining your applications&mdash;so you can spend
more time using what you build, while keeping control of your own
infrastructure.
</p>
</div>
</div>