Alternatives
Products that do what MERN Genie does
Like Create React App, but for your entire stack
- 1
- 2BY
2016 · academy.plot.ly
- 3OA
Hey HN, I'm Nate, the creator of Tamagui. One is a React framework that does two things differently in hopes of simplifying how we build websites and apps: 1. It unifies React Native and React web with typed file system routing by making Vite able to serve RN. This lets you share (or diverge) your code in a simpler way for cross-platform apps. 2. We've partnered with Zero (https://zerosync.dev) to make local-first work well. We've been building a solution in One that makes Zero supporting server rendering, without waterfalls, and with seamless server/client handoff. ---…
2024 · onestack.dev
- 4
- 5
- 6
- 7
- 8
- 9
- 10RO
2016 · github.com
- 11
- 12
- 13PN
2020 · proton-native.js.org
- 14
- 15VA
Introducing v1: a free, open-source starter kit for your next project, built with insights from Midday. This monorepo is designed for rapid development, using the best tools and services available today. It includes Next.js and Supabase for a robust foundation, along with: * Sentry - Error monitoring * Resend - Email delivery * Triggerdotdev - Background jobs * Dub - Sharable links * Upstash - Cache and rate limiting * OpenPanel - Analytics * Polar - Billing * Vercel - Hosting We have handpicked the best libraries in the ecosystem: * Shadcn - UI components * React Email - Email templates *…
2024 · v1.run
- 16
- 17
- 18
- 19VR
Hello everyone, I’ve created this starter project for creating production ready web apps in Vite and React that I hope some might find useful. This template came about as a necessity to provide some standardization across new projects at work. A few of the initial goals when creating this project were to: - Reduce setup time - Standardize codebase with ESLint and Prettier - Improve commit messages with tools like husky, commitizen and commitlint - Improve codebase maintainability and scalability by providing a reasonable folder structure - Simplify React Component development through use of…
2023 · github.com
- 20RS
After accidentally nuking the production database of my last side project, I wished I had used dev/prod environments with automated DB backups. When I looked for a SaaS template to start over with integrated dev/prod environments, I couldn’t find one. So I decided to build it myself. To help speed up the setup, I also built Bash and PowerShell scripts to guide users through the process. The current stack is Next.js, Firebase, and Stripe. However, I’m considering writing some Terraform modules for GCP resources to further speed up setup and provide more flexibility for power users.…
2024 · reactsaas.net
- 21PS
I created Pylon to make it easier to move from hobby projects to full production apps. When I work on hobby projects, I usually use React or Next.js because they are quick to set up and easy to deploy on Vercel. For production apps, I separate the frontend and backend, then deploy the backend on AWS. But setting up a full backend on AWS can be complex and costly, especially for simple apps. Pylon is a full-stack, real-time framework that includes server-rendered React, TypeScript functions, entities, policies, real-time sync, built-in authentication, and support for background and scheduled…
Jul 2026 · pylonsync.com
- 22
- 23LR
Hey HN! I've built a way to launch simple, stateful React components like promotions, banners, and announcements in your web app through reusable in-app UI channels. Here's a demo of how it works: https://youtu.be/qrPip41Ecyg. The docs are here: https://docs.frigade.com/v2/platform/collections. This enables non-technical teammates to launch native, prebuilt components directly in the product UI without involving engineering. We also provide the ability to update content (i.e. CMS), track user progress/state and target components to specific users…
2024
- 24DH
Hey HN, I'm a developer and long-time OSS contributor. Over the years, I've implemented tons of headless CMSs to give product and marketing teams more autonomy. But there's always been a gap with CMSs when it comes to user interfaces. I kept running into the same issues: poor developer experience, bad performance, no support for dynamic content, and needing vendors for AB testing or personalization, which just gets messy and expensive. Versioning? One change and things break or need manual fixes. Accessing your own data? Good luck unless you're ready to pay extra. So, I built a content API…
2024 · docs.croct.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →