








































































































.webp)





















Cosmo Tech provides simulation and digital twin software for industrial operations, helping organizations model scenarios for supply chain, asset, and operations decisions.
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.
Data synchronization frequency is configurable based on your requirements. For real-time needs, Makini supports webhook-based synchronization where changes trigger immediate updates. For scheduled syncing, common intervals range from every 15 minutes to daily, depending on data volume and business requirements. The initial sync after connecting a system retrieves historical data based on your configuration—typically 30-90 days of historical records. Subsequent syncs are incremental, retrieving only records created or modified since the last sync. Sync frequency doesn't affect pricing. You can also trigger manual syncs on-demand via API when needed for specific workflows.
Makini implements automatic retry logic for failed webhook deliveries. If your endpoint is unavailable or returns an error status code, we retry delivery with exponentially increasing intervals starting at 30 seconds. Retries continue for up to 24 hours. If delivery ultimately fails, the webhook is logged but not delivered. You can view failed webhooks in the Makini dashboard and manually retry them. To prevent webhook loss during extended downtime, implement a polling backup strategy—periodically check the sync status and query for recent changes if no webhooks have been received within the expected time window. Design your webhook receiver to be idempotent, as retry logic may result in duplicate deliveries.
Based on our market data, building industrial integrations in-house typically costs $50,000-$150,000+ per integration and takes 2-24 months depending on complexity. Maintenance requires dedicated resources—roughly one full-time person per three integrations. Makini transforms these economics: integrations go live in 1-6 weeks, costs are predictable OPEX rather than large upfront CAPEX, and maintenance is included. You gain access to 2,000+ integrations instead of building them one at a time. Our team has six years of specialization in industrial integrations, meaning we've solved problems you haven't encountered yet. For product companies, Makini allows faster time to market and frees engineering resources to focus on your core product rather than building and maintaining integration infrastructure.
