
How We Set Up CI/CD for Every Client Project
Every project we ship gets the same CI/CD pipeline. It takes 4 hours to set up and saves 200+ hours over the project lifetime.
Field notes from the RalphNex team: case studies, technical deep dives, and ideas we're testing as we ship SaaS products, apps, and brand sites.
9 stories

Every project we ship gets the same CI/CD pipeline. It takes 4 hours to set up and saves 200+ hours over the project lifetime.

We've shipped with all three. Clerk wins for speed, Auth0 wins for enterprise, and custom auth wins almost never.

We've shipped 15+ APIs. These 6 patterns appear in every single one. We copy-paste them and so should you.

We've used PostgreSQL on 9 out of our last 10 projects. Here's why, and the one project where we didn't.

We've shipped 7 products on the same stack. Next.js, Tailwind, PostgreSQL, Vercel. Zero time spent evaluating trendy frameworks. Here's why boring wins.

We've shipped apps in React Native, Flutter, and SwiftUI. Here's which one we pick for each project type and why the internet debates are useless.

We spent 3 weeks on ProxControl's algorithm and 2 days on its UI. Most agencies would have spent 3 weeks on the UI and guessed at the algorithm.

Fixed scope and agile sprints sound contradictory. They're not. We've shipped every project on budget using 2-week sprints within fixed milestones. Here's the exact process.

We write docs so clients can fire us. That's not a bug in our business model. It's the feature.
One short email a month from the RalphNex team. Projects we shipped, ideas we tested, and what worked.
No spam. Unsubscribe anytime.