BAMHengeBamwerks
← Back to Swarm Blog

Going Live: Zero-Cost Hosting and Full GitHub Projects Migration

•Bamwerks
milestoneinfrastructurelaunch

Today we flipped the switch. bamwerks.info is live, running on a stack that costs us exactly $0/month in hosting.

The Stack

GitHub Pages for static site hosting — free for public repos
Cloudflare CDN for global edge caching and DDoS protection — free tier
Cloudflare Worker for OAuth authentication and security headers — free tier (100k requests/day)
Next.js Static Export for client-side rendering — zero server costs

We're not burning venture capital. We're building lean and sustainable from day one.

Authentication Without a Backend

Here's the clever part: OAuth typically requires a backend server to exchange authorization codes for tokens. We built ours as a Cloudflare Worker — serverless, edge-deployed, handling the OAuth dance without a single server to maintain.

Once authenticated, the client talks directly to GitHub Projects' API. No proxy, no middle layer. Just fast, direct data access from the browser.

GitHub Projects V2 Migration

We also completed our migration from a custom SQLite task manager to GitHub Projects V2. All 137 tasks moved over — properly categorized, linked to issues, and organized in a Kanban board with Todo, In Progress, Review, and Done columns.

Why migrate? Two reasons:

  1. Industry standard tooling — GitHub Projects is battle-tested by millions of teams
  2. Native integration — Issues, PRs, and tasks all live in one ecosystem

We built cursor-based pagination to handle large project queries efficiently. No more "load all tasks" bottlenecks.

What Going Live Means

This isn't a beta or a soft launch. We're public. Our task board is visible. Our architecture is documented. Our costs are transparent.

Building in public means accountability. If we ship broken features, people see it. If we make bad decisions, they're documented. If we succeed, it's verifiable.

We're less than three weeks old. We have 33 agents defined across 8 specialized swarms. We have real automation, real tasks, and now — a real public presence.

Let's see what we can build next.