Ax0s
Book a call

Ax0s Live · the connector layer · checked 3 August 2026

The services your business runs.
Already wired in.

"Integrates with everything" is the emptiest sentence in software. So here's the opposite: the actual list of services connected to our own memory today, running on our own business — and for each one, what the connection really does, how often it runs, and where its limits are. This isn't a partner logo wall. It's an operations log.

See the connections ↓ The full register →

Two ways a service
can be connected.

Every row below uses one of two modes, and the difference matters. Flows in (persistent ingest) means the service lands in memory continuously — new emails, meetings and transactions become records on a schedule, whether anyone's at a keyboard or not. Reachable on request (agent access) means an assistant can look something up when asked, but nothing is stored. Vendors blur these two. We label them.

Running on our own business · each row labeled with its real status

What flows in,
and on what terms.

GmailFlows in · 5 min Every email in the connected mailbox becomes a dated, sourced record within five minutes of arriving. Secrets and payment details are stripped before anything is stored. Scope today: one mailbox — ours.
Google CalendarFlows in Events, changes and cancellations land as records, so "when did that meeting actually happen" has a receipt instead of a guess. Redacted like email.
FathomFlows in Meeting recordings and transcripts flow in — what was said on a call becomes searchable memory, with the call it came from attached to every line.
Drive & DocsFlows in Documents become records with their edit history's context. Honest limits, published: text is capped at 20,000 characters per document, and the first sync is budgeted at 300 items per run — big archives arrive over days, not silently truncated.
Mercury (banking)Flows in · read-only Transactions flow in read-only — the connection can see money move, never move it. Account numbers and personal details are redacted. When Mercury's API went down for five hours on 20 July 2026, we wrote that outage into the record too. That's the standard.
SignWell (contracts)Flows in Agreements and their signature states become records — "is it signed, who signed, when" stops being an inbox archaeology project.
StripeSandbox The connector is built and contract-tested, currently running against a test environment. Labeled sandbox until real payment volume flows — we don't call a connection "live" before it is.
iMessageFounders only Our own text threads flow into our own memory — the founders dogfooding the most personal data source first. Unredacted by choice, and only for us; a customer deployment would set its own boundary.
This websiteFlows in Every publication of ax0s.io is itself recorded — what the site claimed, and when, is in the same memory as everything else. The register you're reading is a data source.
Microsoft 365In build Outlook mail and calendar into the same memory. Built and cross-vendor tested as of 30 July 2026. Not yet running against a real account — it gets a "Flows in" row only when it is. QuickBooks Online is next in line.

How hard has this been pushed? Every connector is re-run against a fixed set of scenarios before it ships — 190 + 50 + 140 at last count (14 July 2026), all passing, receipts dated on the register. One anonymized client catalog it has mapped: 147 tables, 1,836 fields, 245,161 rows.

Why the terms matter
more than the logos.

Once these streams land in one memory, the questions that used to take an afternoon take a sentence: "What did we tell this customer, across email and calls and the contract?" — one query, every answer carrying its source. But that's only trustworthy if you know exactly what's flowing in, how often, and what got redacted on the way. That's what this page is for.

The standard each connection meets

Rule— Every record names its source and timestamp — an email, a call, a transaction, never "the system said so." Provenance, always
Rule— Secrets and payment details are stripped before storage, per connector, with the method published. Redaction at the door
Rule— Limits and failures get written down and dated — caps, budgets, outages — not buried. Including the bad days

One memory, many streams

email     ─┐
calendar  ─┤
meetings  ─┼──▶  one store
banking   ─┤     every record dated
contracts ─┘     sourced · redacted

ask       "what did we promise
          Meridian, and where?"
          → answer, with receipts

Your systems already know.
Now they remember.

On a call we'll walk this exact ledger live, then map which of your systems connect first — usually email and calendar in week one.

Walk this ledger against your systems How the memory works →

Checked 3 August 2026. When this page and reality disagree, we fix the page.