Build less. Make more.
Essentials to run Next.js applications in production.
Introducing HappyKit
Building applications with Next.js is fun.
If you've ever built something with Next.js you might have been blown away by its simplicity. I certainly was.
But as you get closer to release, something becomes apparent. There are questions you're not able to answer: Who are your users? How is your application performing? What is your slowest API route? How long does server-side rendering take? How often are API errors returned? Can you roll out a feature gradually? How can you run a certain function once a day?
Now the fun stops.
Next.js is great for building applications, but there's a whole piece missing as you get closer to production. HappyKit wants to be that piece.
Your companion to run Next.js in production — with confidence.
So the fun can continue.
What does it look like?
Who's behind HappyKit?
Hi, I'm Dominik. While working with Next.js, I realized that Next.js is enabling a paradigm shift. The frontend and the backend are moving closer together. This unlocks a completely new category of tightly integrated services.
But existing tools haven't noticed.
They still live in a world where frontend and backend are miles apart. Segregated by location of execution.
So I set out to build drastically better tools. To take advantage of these new capabilities.
The first outcome of that is HappyKit Analytics. I've since gone on to add a feature flagging service called HappyKit Flags and a way to turn your API Routes into Cron Jobs called HappyKit Tasks.
Request access below to get started as HappyKit is currently in beta. I hope you'll enjoy it as much as I do.
— Dominik
Curious?
Request access now.
HappyKit is currently in closed beta. The first product HappyKit launched with is a dead-simple, free analytics service called HappyKit Analytics. Since then, HappyKit Tasks and HappyKit Flags were addded. Request access now as we're gradually letting users in.
