Launching the new kamai.io

The brief for rebuilding kamai.io was short: the site should read the way the product behaves. The old one didn't, so we started over.

What is different

Three decisions shaped the rebuild, and each maps to how Kamai actually works.

• Vector-native, not raster. Most AI takeoff tools flatten a drawing into pixels and run vision over the image, which throws away the line geometry an estimator relies on and turns a clean architectural sheet into a guess. Kamai reads the vectors in the PDF directly, so a wall is a wall and the scale comes from the drawing instead of a screenshot. The new Technology page walks through what that buys you.
• Developer-forward. Plenty of teams want takeoff data feeding their own tools, not living in another dashboard. Public API self-service is on the way, and we shipped a developer hub and an API waitlist so builders can start before it is fully open.
• Content over claims. The blog, customers, and events sections are now first-class, with named customers and the work behind the numbers instead of stock superlatives.

Why now

The estimating shift in AEC is already underway, and the teams pulling ahead treat AI as infrastructure their other tools plug into rather than one more standalone app to babysit. That is the bet behind both Kamai and this site.

If you want to see it run on a real drawing, talk to sales. Fifteen minutes, one of your sheets, no slides.