














































xTuple ERP is an ERP for small and midsize manufacturers and distributors, developed by xTuple, a CAI Software company since 2022. It grew out of the PostBooks project and runs on PostgreSQL, with a Qt desktop client and a REST API served by a Node.js layer. The Distribution, Manufacturing and Enterprise editions cover sales and CRM, inventory, purchasing, shipping and receiving and accounting, with manufacturing in the Manufacturing and Enterprise editions. Planners work with Item Sites, Bills of Materials, Work Orders and Purchase Orders. A production scheduling product reads production orders, which xTuple calls Work Orders, with their bills of materials through Makini's Unified API, so it can see which jobs are Open, Exploded, Released or In-Process. Inventory optimization tools compare stock levels per site with open purchase orders and Purchase Requests to suggest reorder quantities. Sales and CPQ tools read sales orders and customers, and where the connection permits writes, they can push a new sales order into xTuple. An xTuple user signs in through Makini Link, embedded in the vendor's product or sent as a magic link, so credentials never pass through the vendor's application. Data then syncs on an interval set by the Makini plan, not in real time. xTuple grants privileges per user account, module by module or through roles, so ask the customer's administrator for an account with only the privileges the product needs. When the database is hosted on premises, IT can allow Makini's fixed IPs in the firewall or set up a VPN.
Have any questions? We’re here to help You
Some editions of Xtuple expose an API, but it is often limited, legacy, or inconsistent between versions, and many on-prem deployments have no usable API at all. Makini gives you one modern REST API for Xtuple that lets you read and write Xtuple data, even for legacy or on-prem instances. You build against Makini once instead of integrating with Xtuple directly.
You integrate Xtuple through Makini's Unified API. Authenticate once and Makini normalizes Xtuple data into a single consistent schema you can read from and write to inside your product. The same connection reaches Xtuple plus 2,000+ other ERP, WMS and CMMS systems, so you build one integration instead of one per system.
Through Makini you can read and write Xtuple's core records as normalized, standardized resources, in both directions: pull data out of Xtuple and push updates back in. Every field is mapped to a consistent Makini schema, so you work with the same object model across Xtuple and every other connected system.
Days, not quarters. Because Makini already builds and maintains the Xtuple connector, you do not reverse-engineer the integration yourself: you authenticate and start reading and writing Xtuple data through the Unified API, typically within a few days. A Xtuple integration built in-house usually takes months plus ongoing maintenance.
Yes. Makini connects to Xtuple over encrypted connections on SOC 2 Type II certified infrastructure, and handles Xtuple credentials for you so they are never exposed to your app. You authenticate once, and access runs through Makini's managed, auditable layer. The same security model applies across Xtuple and every other connected system.
Makini owns the maintenance. When Xtuple changes its API, versions, or endpoints, Makini updates the connector, and your integration keeps working with no changes on your side. You get a stable Unified API with webhooks, and Xtuple upkeep stays off your roadmap.
