



Have any questions? We’re here to help You
Connection credits are Makini's billing unit. Each system integration consumes a specific number of credits based on complexity. Systems are divided into three tiers: Tier 1 (simple systems like cloud CMMS), Tier 2 (mid-complexity ERP systems), and Tier 3 (complex systems like SAP). On-premises installations require double the credits of their cloud equivalents. For example, a cloud SAP S4/HANA connection might use 4 credits, while an on-premises SAP ECC installation uses 8 credits. Connection credits are consumed when you establish a connection and are returned to your pool when you disconnect. This allows flexible allocation across customers—you're not locked into specific connections.
Design your webhook receiver to handle duplicates and out-of-order webhooks, as network issues or retries can cause both scenarios. Keep the receiver lightweight—ideally writing incoming webhooks to a queue or reliable storage—then process them asynchronously. This prevents timeouts and allows your system to handle high-volume webhook spikes. Respond with a 200 status code immediately after receiving the webhook, before processing begins. Implement idempotency by tracking processed webhook IDs and skipping duplicates. Use constant-time comparison for signature verification to prevent timing attacks. If webhook processing fails, log the error but still return 200 to prevent unnecessary retries. Set up monitoring and alerts for webhook failures so you can investigate issues promptly. For critical workflows, combine webhooks with periodic polling as a fallback mechanism.
Yes, customers can connect as many systems as needed. Each connection is independent with its own API token, allowing you to manage multiple ERP systems, CMMS platforms, or other integrations for a single customer. This is common in organizations with multiple subsidiaries, regional systems, or during migration periods when legacy and new systems run in parallel. Each connection consumes connection credits based on the system type and deployment model. There's no technical limit on the number of connections per customer. For customers using multiple instances of the same system (like regional SAP instances), each instance requires a separate connection with its own credentials and token.
Our standard SLA targets 99.9% uptime for cloud deployments, which translates to less than 9 hours of downtime per year. For enterprise customers with critical integration requirements, we offer enhanced SLAs up to 99.99% through multi-region redundancy and dedicated infrastructure. SLAs cover the Makini platform itself—availability of connected third-party systems is outside our control, though we monitor their health and alert you to issues. For self-hosted deployments, uptime depends on your infrastructure configuration, and we provide architecture guidance to help you achieve your availability targets. We maintain a public status page showing real-time system health and incident history.
