Quick summary:

• Terra Kaffe rebuilt its entire connected coffee machine platform (firmware, cloud backend, communication layer, and mobile apps) in-house, moving off a third-party IoT platform it had used since 2021.
• The migration was necessary because the previous platform partner's support ends December 31, 2026; machines that don't migrate lose internet connectivity until they get a physical WiFi module replacement.
• Some users experienced login issues during the transition, caused by old account credentials that hadn't been used since initial machine setup, which is a common migration snag.
• Affected machines were not lost or damaged; the machine itself had already migrated successfully. Users experiencing issues can contact Terra Kaffe support to resolve them.
• Owning the full stack enables new features going forward: multi-user profiles (Coffee Passport), family profiles, deeper grinder/brew control from the app, GDPR-ready localization, predictive maintenance, ML-driven consumable replenishment, and an AI Barista/Coffee Wizard.

Moving Out: Why We (Re)Built Terra Kaffe's Connected Platform From Scratch

If you've updated your Terra Kaffe app in the last few weeks and your machine suddenly acted like it had never met you before, first: we're sorry. Second, we want to explain because what's happening under the hood right now is one of the biggest technical undertakings in this company's history, and you deserve to know why you felt some of the impact.

We didn't start here

When Terra Kaffe signed on with an outside Internet of Things (IoT) platform back in 2021, it was a reasonable bet for a small company trying to get a connected espresso machine to market. Almost no connected machine talks to its app over Bluetooth alone — you need a WiFi component too, so the machine stays connected from anywhere. Building your own WIFI connectivity firmware (on top of machine firmware), cloud infrastructure, and mobile app from day one is an enormous lift, and partnering with a company that already had that piece built let us focus on the part we excelled at: making a machine that pulls a great shot. That partnership is what got the original TK-02 connected and out the door in 2023.

By the time I joined as CTO in 2022, it was clear the arrangement had a ceiling, and we were already close to it. Terra Kaffe had lofty innovation goals in this category for our connectivity, but ultimately we shipped the TK-02 with a few product compromises we didn't love, not because we didn't know what we wanted to build, but because we were building on someone else's foundation, and there's only so much you can do to a house that isn't yours.

Renting vs. owning

Think of it like your first apartment. It gets you out on your own, and it's genuinely great for a while. But eventually you want to knock down a wall, and you can't, because it isn't your wall to knock down.

Part of the long game for us was always to build and own our own connectivity firmware, the flexibility and control you only get when you're not building inside someone else's box. In 2024, we tried to get there through negotiation with our partner, hoping we could earn the access and support to build what our community actually wanted without starting over from zero. The truth was, the product support we were receiving didn't allow for that, and we wanted to continue our mission to build the best possible products for our community.

That left us with a choice: find another landlord or build our own house.

So, we built our own house

Starting in late 2025, my team and I designed and shipped an entirely new connected platform for Terra Kaffe machines from the ground up in about 10 months. Custom firmware running the WIFI radio hardware. A purpose-built cloud backend on Azure for device communication, Blob storage for everything else, and an entirely new communication schema that allows us both breadth and depth for TK-02’s future roadmap. As well as new mobile apps to tie it all together. Firmware, cloud, communication, and mobile, designed, built, and owned by us, end to end. If you've ever stood up any one of those layers, you know what kind of lift that is on its own. We did all four, at the same time, in under a year, while still supporting the machines already in people's kitchens. I'm genuinely proud of the team for pulling that off, and I say that as someone who was pretty sure at month three that I’d bitten off more than we could chew.

Why now, and why it got a little messy

We had a hard deadline we didn't set ourselves: support from our previous platform partner ends December 31. After that date, any machine that hasn't migrated to our new platform permanently loses the ability to connect to the internet, unless the machine gets a physical WiFi module replacement. That's a fate we wanted to spare as many of you as possible. So, we made a judgment call: launch the migration once the cloud backend and machine firmware were solid, even knowing the mobile app still had some rough edges we hadn't fully sanded down. We'd rather ship something imperfect and fixable, on time than something polished too late to matter for machines that were about to go dark.

What actually went wrong

Here's specifically what tripped people up. When your machine received the firmware OTA update that moved it from the old platform to ours, your existing app (1.0) would prompt you to download the new app (2.0) and migrate your account. Simple in theory. In practice, a lot of people hit that prompt, went to log in, and realized they hadn't touched that password since they first set up the machine. That landed them in an authentication loop between the old OAuth service and our new in-house version: the machine itself had already moved successfully to our new system, but the app hadn't caught up with them yet, so it looked and felt like the machine had vanished. If that happened to you: you didn't do anything wrong, and your machine wasn't actually gone. My engineering team has been manually moving accounts over, restoring settings, and resetting passwords for anyone who calls in. If you're still stuck, reach out to support at [email protected] or 718-738-7488, and we'll get you sorted directly.

Why it was worth it

Owning this stack outright opens up a lot of what we've wanted to build for a while:

• Coffee Passport, letting multiple people share one machine with their own separate profiles and preferences
• Family profiles for personal settings under one account
• Deeper access to your machine's lower-level grinder and brewing functions, straight from the app
• Deeper integration between your machine/the app/your online accounts page, and TK-Hub
• A path to true localization, since our system can be built to GDPR (The European standard for Data Privacy and cross-boarder data traffic) standards, which opens the door to new markets we couldn't reasonably serve before, but have gotten tons of interest from
• Real predictive maintenance, because we now see the telemetry directly instead of through someone else's pipe
• Smarter, Machine Learning-driven replenishment for consumables, so your machine can tell you what it needs before you notice
• TK Coffee wizard and AI Barista to dial in drinks
• Faster, more direct support, because our CX and ops teams can now see exactly what your machine is seeing, instead of waiting on a third party

None of that was realistically possible on a shared platform we didn't control. It is now.

Thanks for bearing with us

Moving is always more disruptive than anyone plans for, even when you're moving into a better place. We appreciate the patience, and if your machine is still giving you trouble, please reach out. We built this so we'd stop having to say "that's up to our platform partner" and start saying "let us fix that," and we intend to make good on it.

Now more than ever, the TK-02 is truly the only coffee machine that keeps getting better year over year.

Vito Di Mercurio, CTO, Terra Kaffe