roastconsole.

Integrations

Your roastery, connected to everything.

From your webstore to your accountant to your AI assistant. RoastConsole plugs into the stack you already run, and opens the record that roastery software usually keeps shut.

Three ways in, and no walled garden.

Most roastery software gives you a CSV export and calls it an integration. Every record here is reachable over an open API, readable by an assistant, and pushed to you the moment it changes.

Open REST API

Every object in the platform on one predictable endpoint. More than 30 entities, keys you scope and revoke yourself, and full read and write.

AI-native MCP

Point Claude, or any assistant that speaks MCP, at your roastery and ask in plain language. Twenty-eight purpose-built tools. Read-only by default; writes only through a key you scope for them.

Signed webhooks

Twenty-four events pushed the moment something changes, each one signed and retried if it fails. Nothing to poll and nothing to miss.

Connected to the tools you already use.

Sell wherever your customers are and keep the books however you already do. An order in one place becomes a packing run, a stock movement, and an invoice that matches.

Start Cloud trial

Square

Point of sale connected per tenant, so counter and market sales stop living in a separate universe from wholesale. Invoices can be sent and collected through Square too, with the payment reconciled against the invoice.

Point of sale and payments

Stripe

Subscription checkout and invoice payment, each one reconciled against the invoice it belongs to.

Payments

Xero

Invoices push to your accountant against your own chart of accounts, and payment status flows back to the order.

Accounting

QuickBooks Online

The same shape as Xero, and a little further: invoices and expenses push across, QuickBooks can send the invoice itself, and payments reconcile back onto the order.

Accounting

Built for control, not lock-in.

The open path is part of the platform rather than a tier you negotiate for. What follows is what makes it safe to leave open.

Keys and access

  • Scoped API keys, issued read-only or read and write
  • Rotate or revoke a key the moment an integration ends
  • Every request scoped to your own tenant at the platform level
  • MCP connections permissioned separately by capability area

Events you can trust

  • Every webhook delivery is signed, so you can verify it came from us
  • Failed deliveries retry rather than disappearing
  • Every attempt stays in a delivery history you can inspect
  • Throttling is per tenant, so one integration cannot starve another

The way out, not just in

  • MCP is read-only unless you issue a write-scoped key, so an assistant changes nothing by default
  • A full tenant export as an archive in open formats, at any time
  • Roasts export to Artisan CSV and .alog, RoastConsole CSV, or an image
  • Artisan, Cropster, and RoastPATH history imports on the way in

Questions

  • Shopify handles order and inventory synchronisation, Square connects point of sale per tenant and can send and collect invoices, Stripe handles subscription checkout and invoice payment, and Xero and QuickBooks Online receive invoices and return payment status. Artisan and Cropster roast history import directly, while RoastPATH .rpath files enter Pilot's reference library.

RoastConsole is live.

Cloud comes with a 14-day trial and no credit card. Pilot is free for Mac. Start with whichever one matches where the work happens.