---
title: Self-host Infra Kit
category: product
entity_type: skill-kit
price: $64
canonical: https://forgehouse.ai/ai-kits/selfhost-infra-kit/
lang: en
hreflang_alt: https://forgehouse.ai/tr/ai-kitler/selfhost-infra-kit/
last_updated: 2026-06-20
---

# 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.

**Price:** $64, one-time purchase, no subscription.

## What's inside
- meilisearch
- reverse-proxy
- uptime-kuma
- plesk
- rank-math

## How to use
Stand up search + proxy, wire monitoring, and manage hosting from one disciplined playbook.

## 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.
1. 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.
2. 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.
3. Uptime Kuma monitoring watches the running stack and reports downtime to you before the customer notices it, so the alert reaches you first.
4. 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.
5. 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.

What the stack hands you
- SEARCH: self-hosted · off the paid service
- PROXY: chosen · benchmark settled it
- UPTIME: watched · alert reaches you first
- WP OPS: automated · panel chores routined

## Field case, The search bill that left the building (2026)
Problem: Search ran on a paid third-party service, so a core feature sat behind someone else's invoice and someone else's uptime.
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.
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.

## Who it is for
- 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

## Proof
The self-host setup you run on your own server (e.g. Hetzner): search, monitoring and panel ops included.

---
Maker: Can Davarcı, https://candavarci.com.tr
