terraceIQ is what happened when a portfolio operator who also happens to be a career software engineer stopped waiting for someone else to build the right tool.
I've spent more than twenty years as a senior software engineer. Alongside that career, I built MKN Properties, where our team of engineers and investors owns and manages hundreds of rental units.
For years we ran that portfolio the way everyone does — on the big-name platforms. All of them worked, technically. None of them worked the way we did. The software was complicated: features buried three menus deep, training courses for things that should be obvious. And the pricing was modular — e-signing was an add-on, screening was an add-on, and the invoice grew every time we tried to do our jobs.
I wanted one thing: software that's simple, easy to use, and very fast. Nobody sold it. So we built it. terraceIQ is the system MKN Properties actually runs on — every feature ships to our own portfolio before it ships to anyone else's.
Because I write software for a living, I had opinions about the engineering, too. The architecture is state of the art and entirely ours — no third-party modules, no plugins we don't control, no inherited zero-day exposure, nothing bolted on to slow it down. That's why the app is fast, and why it stays fast at ten units or ten thousand.
The business decisions follow the same logic. One flat price, because I hated per-unit math. Check printing, because deposits still leave on paper sometimes. An audit log as a first-class feature, because when money moves you should be able to see exactly who did what. And when you email support, you reach people who manage property — often me.
Free migration from AppFolio, Buildium, Yardi, or spreadsheets — and a founder on the other end of the email.