pixelysg/mike
pixelysg is reshaping Mike's plumbing so it runs cleanly on Cloudflare, talks straight to Postgres, and reaches Claude through Amazon Bedrock.
This fork is an infrastructure-focused take on Mike from pixelysg. Rather than reworking the product surface, the work so far concentrates on where and how Mike runs - getting it deploying smoothly on Cloudflare Workers, opening up a direct Postgres path, and adding Amazon Bedrock as another route to Claude.
The shape of the work suggests pixelysg is fitting Mike into a specific operational stack: one where Cloudflare hosts the app, Postgres is reachable on its own terms without a Supabase intermediary, and the AWS account is already the natural home for model calls. It reads less like a product rebrand and more like a deployment story being worked out in public.
If you're curious how Mike behaves outside its default hosting assumptions, this is a fork worth a click through to GitHub.
What's in it
- Cloudflare Workers deployment Work to get the fork building and shipping cleanly on Cloudflare's edge runtime.
- Direct Postgres connection An optional path that lets the app talk to Postgres directly, with Supabase taken out of the middle.
- Amazon Bedrock as a Claude provider A fourth way to reach Claude, routed through AWS for teams already operating there.
Direction
infrastructureintegration
Activity
Threads of work (detailed view)
pixelysg routes Mike through Amazon's cloud
A fourth way to reach Claude - this time via AWS - for shops that already live there.
pixelysg cuts out the Supabase middleman for database calls
An optional toggle lets the app talk to Postgres directly while keeping the rest of the codebase none the wiser.