caffeine

What changes have occurred?
Three plans instead of four, each with a clear goal:
Free - Check out what you can create with Caffeine
Host - Your application, live online
Studio - Designed for developers who are constantly building
Why do we need three plans?
The original four-tier plan left people guessing which one they were choosing, while the new plans clearly state the purpose of each option, making the choice straightforward.
What’s the price?
Save 20% every year.
What’s the difference between Host and Studio?
Both allow you to build using chat features, mix from the app marketplace, create projects from scratch, publish your app on your own domain, and send emails to your users.

Use your existing domain to develop your Caffeine app.
Now you can connect your existing domain to any Caffeine project. If your domain registrar is GoDaddy, Namecheap, or any other, just throw in a few DNS records to point it to your app.
Caffeine will give you the exact records you need to add and where to put them—no guesswork, and no need to manually hunt for DNS info.
Your domain registration status stays unchanged, no need for any transfers or handover of admin rights. Once the DNS records go live (usually within a few hours, but sometimes it can take up to 24 hours), your app will be live at your own address, and your original caffeine.xyz URL will still be valid, so there won’t be any hiccups in the process.

This is the first article in a series about the updates in Caffeine V3; this piece will introduce the new build architecture. Stay tuned for the next one: how V3's design system creates more aesthetically pleasing apps.
If you've ever faced the situation where Caffeine, after 50 tweaks, forgot what your app originally looked like, here's the scoop on why that happened and why it won't be an issue moving forward.
In the V3 version, we've completely revamped the way Caffeine builds apps. Previously, Caffeine operated on a sequential pipeline, essentially a series of proxies running one after the other: planning the app, building the backend, building the frontend, running quality checks, and deploying. Each step had to be completed before kicking off the next one, and if the third step found issues with the second, there was no rollback.