Kyle Cunningham

GTM vibecoding update: Goodbye Supabase. Hello, Railway. Why I'm switching. I used Supabase because bolt.new made the setup dead simple. And it was. But as I scaled, Supabase's pricing got out of sync with the value it creates. It charges for 3 things: 1. Platform 2. Usage (multiple types–functions, bandwidth, other stuff I didn't care enough to learn) 3. Add ons (don't think I use these–but maybe?) For the skyp ai marketing site, it was great to get it set up. Built into Bolt, super fast. I have edge functions running to connect a beehiiv with the site so we get more SEO juice (not something you can do with Substack, to my knowledge). See Tyler Denk 🐝 there's a cool behiiv feature that isn't related to dashboards 😎 Supabase has limitations–no proper server infrastructure. But it works for what I was doing. Or I made it work. Setup was a breeze. Using Supabase I built a powerful progressive capture signup form that would have cost $100/mo on Typeform. Edge functions do a lot in the background–newsletter stuff, qualification stuff. It does what I need it to and was (basically) free. Until I vibecoded 2 other projects. I was pushed into a "Pro" account. You're forced to upgrade on your 3rd project. It's $25 for an account. Then every additional project costs $10 + usage. If you're experimenting as much as I am, that could easily hit $100s/mo. Even if that project is kleenex software–something I use once and throw away. Now Supabase has this $10 tax. Forever. Unless you click the big red DELETE Button. Or what, download it and do a migration later? Crazy talk. I get $10 for "Production". What about "Screwing around"? I get charged the same for everything. It's either on or off, and I'm not actually sure if the charges stop for a paused project. Maybe they do? I have more important things to think about. So, congrats Supabase, your pricing extracted probably more than you should have from me. For a few months. Now i'm going to go scale over at Railway. I moved new projects over there a while ago. I stopped adding Supabase projects when each one cost me $10. Setup was harder–but worth it. I built an entire CRM from scratch. It costs, well, $0 to operate. Now I'm going to do a migration. And by "I'm going to" I really mean Bolt and Cursor are going to, and I'm going to watch. We're all figuring out this AI pricing thing. I've got ideas, if you want to hear them, just DM me. Or talk to Marcos Rivera. But this current model isn't working for you Supabase. Even if you think it is.

6

Guide to White-Label Web Development for Singapore Agencies Singapore’s design agencies are growing fast — but development timelines, hiring costs, and client expectations are growing even faster. That’s why more agencies now rely on white-label web development partners to build websites quickly, privately, and profitably. Read blog: https://lnkd.in/dhh9EWV5 #singapore #agency #outsourcing #partner #development

1

2 ความคิดเห็น

[Dev identity shift] I recently drafted this for the team at Dwarves, and I think it’s a conversation worth bringing to the broader community. The role of a developer is changing fast. In the near future, we’ll be expected to take on fullstack responsibilities, blending multiple hats across architecture, product, operations, and data. Here’s how I see the shift: + Architect: Moving from writing code to defining what should be built. + Product: Shifting from shipping features to uncovering user needs. + Operations: Evolving from creating outputs to orchestrating AI systems. + Data: Transitioning from generating code to curating understanding. If you’ve worked with coding agents like Claude, this probably feels familiar. Once you can plan with enough detail, the agents do the heavy lifting. I’ve watched as a single well-designed plan can set off a swarm of sub-agents working tirelessly in the background. Where do you see your own developer identity heading? Are you embracing these new roles, or do you see the landscape differently? https://lnkd.in/eM3fU9dB #SoftwareDevelopment #AI #Fullstack #DeveloperJourney #TechTrends #TeamDwarves #Innovation #FutureOfWork

10

⚡ Another big win for Web Performance and Core Web Vitals! The latest Safari Technology Preview (version 229) now supports the INP (Interaction to Next Paint) metric with the Event Timing API: https://lnkd.in/gmrEFcFC If you're already using SpeedVitals RUM, you can now monitor INP on Safari Technology Preview. Now we’re closer than ever to having full cross-browser support for Core Web Vitals (and I hope CLS gets included in Interop 2026 as well!) If you wish to check the INP numbers on Safari, give SpeedVitals RUM a try 👉 https://lnkd.in/dc223RKF #WebPerf #CoreWebVitals #Safari #RUM #SEO

50

2 ความคิดเห็น

Due to connection limitations we didn't anticipate, we are currently increasing server capacity for both SMC DAO App and Peniwallet. This should solve alot of the minor issues across both apps.

3