Projects

A living index of systems, experiments, and operational notes.

The goal is not to show polished case studies. It is to keep a useful record of what exists, what was learned, and which parts are safe to reuse.

Showing 4 projects

Live boundary Cloudflare

Cloudflare + VPS split

The root domain stays static and fast, while admin panels, API services, and experiments are isolated behind explicit paths or subdomains.

Reusable
The public identity site can stay stable even when server-backed demos are added, removed, or restarted.
Next
Move the static root to Cloudflare Pages when the content workflow is stable.
  • Cloudflare
  • Caddy
  • VPS
Open record
Research map AI tooling

AI gateway research index

A structure for turning scattered notes about clients, proxy patterns, OAuth flows, and routing tools into public references.

Reusable
Useful judgment is separated from fragile implementation details and account-specific experiments.
Next
Publish a comparison template for evaluating AI clients and routing layers.
  • AI tooling
  • Routing
  • Research
Open record
Running Astro

Personal publishing system

A bilingual Astro site with structured project data, SEO metadata, static output, and a low-friction path for adding new notes.

Reusable
The domain becomes a durable home base instead of a temporary server placeholder.
Next
Replace placeholder notes with screenshots, decisions, and public changelogs from real work.
  • Astro
  • SEO
  • Bilingual
Open record
Checklist Security

Small service hardening loop

A repeatable checklist for exposing dashboards and tools without accidentally widening the public attack surface.

Reusable
Documents routes, headers, backups, logs, secrets, and rollback before a service is linked from the homepage.
Next
Turn the checklist into a pre-publish template for every future demo.
  • Security
  • Caddy
  • Ops
Open record

Deployment stance

The root domain stays boring. Experiments get their own boundaries.

The public homepage is static. Admin panels, APIs, and service demos should live behind explicit routes or subdomains, so a broken experiment does not damage the identity site.