




Have any questions? We’re here to help You
Makini supports over 2,000 industrial systems across ERP, CMMS, and WMS categories. This includes major platforms like SAP (ECC, S4/HANA, Business One), Oracle NetSuite, Microsoft Dynamics, IBM Maximo, and specialized industrial systems. We support both cloud-based and on-premises installations. If you need to connect to a system we don't currently support, we're committed to building that integration for you at no additional charge—most new integrations are completed within one business day. You can view our full list of supported systems at makini.io/integrations.
Industrial systems are often heavily customized, and Makini is built to handle this. For reading data, Makini can access virtually any field or custom table in connected systems. Through the connection settings interface, you can specify custom fields, tables, or entities to include in API responses. These show up alongside standard fields in the unified model. For custom objects not in our default model, you can request them through the interface and they'll be available immediately. For writing data, customization support varies by system but covers most common scenarios. During implementation, we work with you to identify required customizations and ensure they're properly configured before going live.
When a system becomes unavailable, Makini detects the connectivity failure and marks the connection status accordingly. Scheduled syncs will fail with connectivity errors. API requests to the connection will return error responses indicating the system is unreachable. Makini continues attempting scheduled syncs using exponential backoff—initial retries happen frequently, then progressively less often to avoid overwhelming the system when it comes back online. Webhooks notify you of the connection status change. When the system comes back online, normal operations resume automatically. For temporary outages, no action is required. For extended outages, you may want to notify the customer. Connection credits remain consumed during outages since the connection configuration persists.
Yes, Makini supports multi-region deployments for customers requiring data residency in specific regions or needing high availability across geographies. Each region runs an independent instance of Makini with its own infrastructure, ensuring data remains within the specified region. Multi-region deployments are most common for self-hosted installations where customers want instances in multiple AWS regions or data centers. For cloud deployments, we can discuss region-specific hosting based on your requirements. Multi-region support ensures compliance with data localization regulations and provides geographic redundancy for mission-critical integrations.
