[grade=A] Add founder story to DashCaddy About
This commit is contained in:
1 file changed
+41
-22
+41
-22
@@ -23,38 +23,57 @@ export default function AboutPage() {
|
|||||||
</div>
|
</div>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
{/* Story */}
|
{/* Founder Story */}
|
||||||
<section className="py-20 px-4">
|
<section className="py-20 px-4">
|
||||||
<div className="max-w-3xl mx-auto">
|
<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">
|
<div className="space-y-4 text-surface-300 leading-relaxed">
|
||||||
<p>
|
<p>
|
||||||
Self-hosting is powerful. You own your data, you control your
|
I'm Sami Ahmed, the creator of DashCaddy. I built it because
|
||||||
infrastructure, and you're not at the mercy of SaaS
|
I wanted a simpler, more organized way to manage the applications
|
||||||
providers who can change their terms, raise prices, or shut down
|
and services running on my own network.
|
||||||
overnight. But let's be honest — it can also be a
|
|
||||||
pain.
|
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
Every new service means editing Caddyfiles, creating DNS
|
The project's roots go back to 2024. What began as a personal
|
||||||
records, configuring SSL certificates, writing Docker Compose
|
dashboard gradually developed into a broader idea: adding an
|
||||||
files, and hoping everything plays nicely together. Multiply that
|
application should also take care of the configuration needed to
|
||||||
by 20, 30, or 50 services, and you've got a full-time
|
make it accessible.
|
||||||
operations job on your hands.
|
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
DashCaddy was built to solve this. One click to deploy an app.
|
Working with my own infrastructure shaped that vision. Managing
|
||||||
SSL, DNS, and reverse proxy configuration happen automatically.
|
reverse proxies, certificates, DNS records, and individual
|
||||||
A beautiful dashboard with real-time WebSocket updates to monitor
|
services showed me how much repetitive work self-hosting can
|
||||||
everything. Natural language AI commands so you can just say
|
involve. Choosing Caddy helped establish the foundation for the
|
||||||
“deploy Plex” and it happens. And when something
|
project that became DashCaddy.
|
||||||
goes wrong, you know about it immediately — not when a
|
|
||||||
family member texts you that Plex is down.
|
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
We believe self-hosting should be accessible to everyone, not
|
Since then, DashCaddy has grown beyond a service directory into a
|
||||||
just people who enjoy writing YAML at 2 AM. DashCaddy makes it
|
platform for deploying applications, managing connectivity,
|
||||||
beautiful, effortless, and intelligent.
|
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'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's mission is to make homelabbing more accessible.
|
||||||
|
Whether you'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—so you can spend
|
||||||
|
more time using what you build, while keeping control of your own
|
||||||
|
infrastructure.
|
||||||
</p>
|
</p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|||||||
Reference in new issue
Block a user