Proof first: every claim here traces to real client work at candavarci.com.tr.
Self-host Infra Kit
Own your stack: search, proxy, uptime, panel.
Five infrastructure skills for teams who self-host: Meilisearch, a reverse proxy, Uptime-Kuma monitoring, Plesk operations and Rank Math.
$64
Not a promise. A record.
Run the playbook. Then hold the records up to the light.
how to run it
Stand up search + proxy
Wire monitoring
And manage hosting from one disciplined playbook
The self-host setup you run on your own server (e.g. Hetzner): search, monitoring and panel ops included.
brands this system has worked for · 200+ clients
Inside the run · no black box
How the stack runs on a box you own
This kit is not a pile of services you rent. It is a self-host stack on your own Hetzner box, where each part owns one layer and hands a working surface to the next.
- Customer Meilisearch Selfhost takes the search layer off a paid service and runs it on your own box, so query and index stay under your roof instead of behind someone else's invoice.
- Hetzner Reverse Proxy Benchmark settles the routing layer by measurement, not opinion. It tests the proxy options and hands back the one that actually performs on your box.
- Uptime Kuma monitoring watches the running stack and reports downtime to you before the customer notices it, so the alert reaches you first.
- WordPress Plesk Automation takes the panel chores, the repeat operations on the WordPress and Plesk side, and runs them as a routine instead of by hand.
- WordPress Rank Math MCP Bulk handles the SEO field work in bulk, applying changes across many pages at once instead of one screen at a time.
SEARCH: self-hosted · off the paid service
PROXY: chosen · benchmark settled it
UPTIME: watched · alert reaches you first
WP OPS: automated · panel chores routined
One power source. 6 lines out.
selfhost-infra-kit · core
core active · 6 lines
- ✓ using a kit of claude sk…
Using a kit of Claude skills to stand up fast, typo-tolerant site search that respects Turkish characters
- ✓ choosing between caddy
Choosing between Caddy, Nginx and Traefik with real benchmark data, not opinions
- ✓ monitoring dozens of cli…
Monitoring dozens of client sites from one dashboard with a public status page
- ✓ automating wordpress bac…
Automating WordPress backups, staging clones and safe deploys on Plesk
- ✓ bulk-updating seo meta and
Bulk-updating SEO meta and schema across 500+ WordPress pages, backup-first
- ✓ cutting a per-query saas
Cutting a per-query SaaS search or hosted-monitoring bill down to a flat monthly cost
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Own your data and your stack on your own server: no vendor lock-in, no surprise pricing tiers
license: perpetual -
Trade per-search and per-monitor SaaS bills for one flat, predictable cost
license: perpetual -
Every infra change is reversible: backup-first, dry-run-first, idempotent by default
license: perpetual -
Find out about downtime and expiring certificates before your client does
license: perpetual -
Faster server response and tuned TLS that lift Core Web Vitals directly
license: perpetual
subscriptions expire · deeds don't
Five parts. One line.
Watch the work travel, every station is a product you could buy alone. Together, they run as one.
meilisearch
view part →reverse-proxy
view part → uptime-kuma
view part → plesk
view part →rank-math
view part → every part also sold alone, the line is the discount.
Everything in the box.
Pick a piece up. Watch it work.
meilisearch
5 parts · one working system · ships instantly by email
From the field · a real case
The search bill that left the building
2026 · The problem
Search ran on a paid third-party service, so a core feature sat behind someone else's invoice and someone else's uptime.
The fix
Customer Meilisearch Selfhost moved the search layer onto the Hetzner box, the reverse proxy choice was settled by benchmark, and Uptime Kuma was set to report any outage before the customer saw it.
The result
Search now runs on a box we own, the routing choice rests on measurement instead of a guess, and downtime reaches us before it reaches the customer.
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
Agencies and operators managing many client sites who want to self-host with discipline · Engineers weighing self-host against managed hosting who need a cost-backed decision · Teams who need Turkish-aware search, monitoring and WordPress ops under their own control
then this was forged for you.Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
Why self-host search instead of using a hosted service?
Because a hosted search service keeps a core feature behind an external invoice and an uptime you do not control. Customer Meilisearch Selfhost puts query and index on your own Hetzner box, so the search layer stays under your roof.
-
How is the reverse proxy choice decided?
By measurement, not preference. The Hetzner Reverse Proxy Benchmark tests the proxy options on the actual box and hands back the one that performs, so the routing layer rests on data rather than a default pick.
-
What does the Uptime Kuma piece change in practice?
It changes who finds out first. The monitor watches the running stack and reports an outage to you before the customer notices, so a problem becomes an alert you act on rather than a complaint you answer.
-
Any refunds?
No refunds, every claim is proven before you buy. The proof is your safety net.
-
How is it delivered?
A file + install guide, instantly by email. No account needed.
-
Does it only work with Claude?
No. The format is open and the file is plain text, so Claude, ChatGPT, Gemini or Cursor each adapt it their own way.