Skip to content
TEGAR-AJA avatar

Blog

Infrastructure as a product, not a pile of servers

Why Kilat Cloud is built as an abstraction layer — API-driven provisioning instead of manual config.

CloudPlatformKilat Cloud

Manual server configuration doesn't scale. Kilat Cloud treats infrastructure as a product: customer console, billing, wallet, automated provisioning, provider abstraction, monitoring, and audit logging — all API-driven.

The provisioning pipeline follows request validation → preflight → balance hold → queue → worker → provider API → sync → ledger → audit. Every step is observable and repeatable.

Long-term that means owning more of the stack: ASN, IPv4/IPv6, BGP, RPKI, Internet Exchange, colocation — from reselling upstream toward independent network infrastructure.

Read more

Troubleshooting across the full stack

App → OS → storage → network → virtualization → hardware → provider. Real incidents rarely respect layer boundaries.

What managing 40+ Linux servers taught me

Patterns from enterprise/dedicated server operations: monitoring, failover, automation, and out-of-band hardware.

Why I ship static-first when I can

Static HTML is still undefeated for content sites — here's how I decide when to reach for it.

Your GitHub is a portfolio — treat it like one

187 public repos: consistency and good READMEs matter more than any single flashy project.

Accessible by default, not as an audit

Focus states, contrast, and semantics are cheaper to bake in than to retrofit.

Performance budgets that actually stick

Setting a number is easy. Keeping it green takes tooling and culture.

From side project to something people use

The unsexy work: auth, error states, empty states, docs — the gap between demo and product.

← All posts