Build log/2026-09-28·2 min read

MakanCloud v8.34.0 is live: this time, all the changes are under the hood

When restaurant owners size up a system, most start with the obvious stuff: does it look nice, how many buttons does it have. After using it for a while, they realize what matters more: can you trace a problem when something goes wrong, is your data stored safely, and do the rules work the same way every time.

On September 27, we shipped MakanCloud v8.34.0. This release mostly covers phase five of the HR module. There aren't many new features. Nearly every change is in places you won't see.

1. Locking in a batch of open rules

By this point in HR module development, we'd built up a backlog of business rules that still needed a decision. In this release we settled all of them, built them into the system, and updated the docs to match.

For outlets, this means the same kind of situation now gets handled the same way every time. The outcome won't change just because a different person is handling it or it happens on a different day.

2. Security review first, then ship

Changes pass a security review gate first: dashboards require a declared role, operations get a source marker, and the old channel is closed before going live

Before going live, we ran a dedicated security review on this batch of changes and fixed three things:

Viewing a dashboard now requires a declared role: the system has to know who's looking and in what capacity. Nothing gets waved through by default.
Platform operator checks now carry a source marker: actions on the platform side record how they were performed, so they're easy to tell apart when you trace things back later.
An old channel is closed: we shut down an entry point left over from legacy logic.

This is how we've always worked at MakanCloud: every iteration gets a security audit, and in our cross-tenant penetration tests every attempt was blocked, with zero leaks.

3. Opening data imports you can trace batch by batch

The most painful part of switching systems is moving your existing data over. This release adds per-batch auditing to the opening-balance import script. Every batch now gets a record, so if one goes wrong, you can go straight to it.

4. Private files moved to a separate encrypted disk

After business hours: take a snapshot, confirm rollback works, then migrate private files to a separate encrypted disk and approve the release

We moved the private files directory onto its own encrypted disk. We did the whole thing after business hours. Before deploying, we took a snapshot and confirmed we could roll back, and only then approved the release.

Anyone in F&B knows nothing can go wrong during peak hours. The same goes for system maintenance: you don't touch anything while outlets are at their busiest.

Wrapping up

This release doesn't give us any nice screenshots to show off, but a system you plan to use for years depends on exactly this kind of work.

How are you managing staff records and scheduling right now? Let us know in the comments. We read every one.

If you'd like to try it yourself, MakanCloud offers a 14-day free Pro trial. No credit card needed, and initial setup takes about 5 minutes: https://makancloud.com/register