Makini

Connect to industrial systems via one API

4 followers

Visit website
Makini is the REST API for industrial systems. Tech companies use it to connect with industrial systems of their customers, regardless of what system it is - all via one simple API. It’s like Plaid, but for industrials.
Makini gallery image
Makini gallery image
Makini gallery image
Free Options
Launch tags:
API•Developer Tools
Launch Team

What do you think? …

Darius Cheung
interesting, tackling an ancient industry with modern API approach.. like plaid but for old hardware industry?
George Surovtsev
Maker
@darius_cheung Plaid is my fav analogy tbh! Just swap banks with industrial systems and fintech apps with industrial ones and you'll get Makini :)
George Surovtsev
Maker
@darius_cheung if you want more analogies, can suggest Impala (hotel systems), finch (payroll systems), or merge (accounting and payroll systems) :))
George Surovtsev
Maker
Hey Product Hunt! So excited to have @pollock hunt us, thank you! 🎉 I’m the co-founder of Makini along with @roman_kinyakin. Industrial tech companies use Makini API to connect with industrial software systems of their customers, no matter what system it is - all via one, simple API. It's like Plaid but for industrials. Why we built Makini? There are so many amazing industrial tech products making a real difference, but they have a hard time scaling. These are the products that: 🩸 save people from injuries 🛢 reduce impact on environment 💥 prevent breakdowns The scaling problem is that modern facilities already use tons of software. And when you bring in new tech, they don't want to change their process, they want you to fit into it. What it means for industrial tech? - building tons of integrations. Building one costs $30k, takes up to 18 months. Now imagine doing this hundreds of times. For many companies this is not feasible. We integrate with hundreds of these industrial systems in advance and expose one, simple API. So you don't have to deal with legacy systems, figure out business logic, and can concentrate on your core product instead of building (stupid) integrations. 🙏 All feedback helps a ton so please comment and let us know what you think! 🙏 Note: As founders we still onboard each and every user, guide them through, and make sure everyone gets an awesome experience. We'd love to meet you! 👋
Sanjukt Saha
@pollock @roman_kinyakin @george_surovtsev This is hardcore. Bring it to India.
James Robins
Let’s say I’m an app that wants to connect to systems via Makini, how much control do my customers have about how much data they are sharing with me?
George Surovtsev
Maker
@jrobins6 There are 2 things that matter: end-points; and what equipment you are given access to. • End-points: depends on what end-points are included in your plan for the app. Also. when end-users authenticate they see what classes of data you will get access to. • What equipment: controlled by number of assets in your plan, and end-users actually select what equipment they want to give access to. You can then request more or deselect.