Integrations

Ten systems we connect most

These are the systems teams ask about most. The honest rule: if an official or community server already covers your case, we say so and point you at it, because a custom build you did not need is a bad sale. We publish one write-up at a time, with the actual tools we would define. Postgres is up; the rest are in the queue rather than mass-produced, because ten thin pages would help nobody.

• Postgres

  Custom adds a read replica, a least-privilege role, query guards and no DDL. This is the one we have written up.

• MySQL

  Same read-safety story as Postgres; the guards differ. Researched next.

  Write-up pending

• HubSpot

  A native option exists; custom is worth it where it stops. Write-up pending.

  Write-up pending

• Salesforce

  Object and permission model makes curation matter. Write-up pending.

  Write-up pending

• Shopify

  Order, inventory and customer tools, with PII handling. Write-up pending.

  Write-up pending

• WooCommerce

  The reference build runs on WooCommerce data. Write-up pending.

  Write-up pending

• Stripe

  The case where read-only should be absolute. Write-up pending.

  Write-up pending

• Jira

  Trackers are where tool-count bloat is worst; query-shaped tools fix it. Pending.

  Write-up pending

• Notion

  Search and read tools first; writes are the careful part. Pending.

  Write-up pending

• Zendesk

  Ticket read plus a safe comment-write. Write-up pending.

  Write-up pending