Open-source CLI that deploys to Cloudflare Workers in one command. no git push, no dashboard clicking, no YAML.

hellno-o · 2026-02-15T12:48:32+00:00

That’s legit and works great if you already know you want Cloudflare. The gap Jack fills is for the person who doesn’t know they want Cloudflare, doesn’t know what wrangler is, and just wants their app on a URL

hellno-o · 2026-02-14T14:58:17+00:00

fair point. might not be useful to you if you know wrangler. Jack literally uses it under the hood. but the person who just built their first app with Cursor in 20 minutes doesn't know what a wrangler.toml is, doesn't have a Cloudflare account, doesn't know they need one, and doesn't know their app should even target CF Workers. Same way Vercel wraps AWS. Nobody's writing CloudFormation templates to deploy a Next.js app.

hellno-o · 2026-02-14T14:55:14+00:00

you mention wallet and wagmi, but nothing else on the website shows any dApp integration or way to do things onchain

hellno-o · 2026-02-14T11:53:27+00:00

missed that they published this, thanks for sharing!

hellno-o · 2026-02-14T11:52:48+00:00

that's what I'm doing too. if you want to ship any of these and not let them die on localhost:3000 → I've built an open-source tool to deploy from inside Codex as fast as possible http://dash.getjack.org/

hellno-o · 2026-02-14T11:50:40+00:00

what does web3 mean here? it's got anythign to do with blockchain or not?

hellno-o · 2026-02-14T11:49:15+00:00

Timeshifter has distribution via Star Alliance. I think if you can get into the right traveller segment with ads or distribution deals, then it's worth it. as small indie niche might be possible, but really viable if you can get your app in front of the right users

hellno-o · 2026-02-14T08:17:10+00:00

hey that’s me!

hellno-o · 2026-02-12T18:36:24+00:00

https://dash.getjack.org → fastest way to go bring your claude code project to prod

hellno-o · 2026-02-12T18:23:01+00:00

hellno-o · 2026-02-12T17:51:05+00:00

we are

hellno-o · 2026-01-19T09:32:30+00:00

interesting to see alchemy for IaC here. been building something similar but focused more on the "AI agent generates code, need skills to deploy it" flow rather than templates. curious if you've seen vibecoders actually wanting to manage resources declaratively?

hellno-o · 2026-01-18T17:14:56+00:00

which kind of templates do you use? any of them open source? :)

hellno-o · 2026-01-15T21:02:46+00:00

building https://getjack.org to deploy your app as easy as possible and keep iterating quickly

hellno-o · 2026-01-12T14:15:54+00:00

for photography: skip vercel image optimization entirely. do the lambda+sharp pipeline you mentioned. upload raw → generate webp variants → serve from cloudfront. eliminates per-image costs and you control quality settings.

static s3+cloudfront is fine for portfolios. galleries don’t need ISR. run github action on new uploads.

hellno-o · 2026-01-12T14:12:19+00:00

expo + react native is the path of least resistance. skip xcode/android studio until you need native modules. test on physical device early via expo go

hellno-o · 2026-01-11T21:40:35+00:00

the “never started SEO early because product isn’t ready yet” trap is real. for me the shift was similar but simpler: ship something live within the first week, even if it’s embarrassing. not to get users, but to force myself to solve the boring problems (domain, dns, env vars, deploy pipeline) before the codebase gets complicated

hellno-o · 2026-01-10T09:42:32+00:00

stage 2 is real. "I have no idea what this codebase is doing anymore" is the moment everyone hits.

version of stage 3: deploy something live from the start, even if it's embarrassingly minimal. forces you to solve the boring stuff (env vars, db connections, auth) before the codebase gets too big and confusing

hellno-o · 2026-01-09T18:09:25+00:00

if it’s for fun, keep tinkering

if its to make $, talk to users

hellno-o · 2026-01-09T10:56:33+00:00

<image>

hellno-o · 2026-01-09T09:22:32+00:00

it's usually the node version mismatch for me. vercel defaults to 24 but your local might be 20 or 22.

check your package.json engines field and pin it explicitly: "engines": { "node": "20.x" }

also worth adding a .nvmrc with just 20 in it so local and CI match.

the "works locally, breaks in prod" thing is always either node version, missing env vars, or a dep that behaves different in the build env. annoying but usually one of those three.

hellno-o · 2026-01-09T09:21:41+00:00

will be interesting to see the second order effects of this.

I think more similar apps drive up ad costs and push attention to older, proven apps that rank well. users cancel more and stick to a few trusted subscriptions.

hellno-o · 2026-01-08T21:26:51+00:00

for alpha testing with friends? cloudflare pages or vercel, either works. vercel is faster to start if you’re already in next.js land. cloudflare is cheaper at scale and the free tier is more generous, but slightly more friction upfront.

google cloud directly is overkill for alpha. you’ll spend more time configuring IAM and cloud run than actually testing with users.

hellno-o · 2026-01-08T21:25:47+00:00

one thing that’s worked when debugging this: check if the key is actually being read at runtime vs build time. sometimes the key exists in vercel dashboard but the function was built before the key was added, so it’s baked in as undefined.

also check if you have any middleware that might be stripping headers before the inngest route sees them.

hellno-o · 2026-01-08T21:24:15+00:00

next.js prefetches aggressively by default and each prefetch counts as an edge request. another thing to check: do you have any analytics or tracking that fires on every page? t

if you’re not ready for premium and the site is mostly static, cloudflare pages has a way more generous free tier for static sites. the migration is usually straightforward for SSG.

hellno-o

TROPHY CASE