Your systems already hold the answer.
They just hold it in nine different places, in nine different shapes, and none of them talk to each other. A connection is how VibeCFO takes one of those and makes it answerable - on its own, and next to every other one.
Not everything connects the same way.
Most vendors show one logo wall and let you assume it all works alike. It does not. Something that lands your ledger every night is a different animal to something that reads a contract, and both are different again to something that reaches out and files a task for you.
Integrations
READS INPurpose-built pipelines into the systems you already run
Integrations →Action MCPs
ACTS OUTEVA reaches into another system and does something
Action MCPs →Databases
READS INYour own SQL, read directly and joined to everything else
Databases →Datasets
READS INSpreadsheets and CSVs that never had a system to live in
Datasets →Documents
READS INContracts, leases and policies she can read and cite
Documents →Websites
READS INPublic pages worth watching, read on a schedule
Websites →Every system we have built a pipeline for.
Generated from the connection registry, so it is what engineering has actually shipped rather than what marketing hopes. Each one has its own page with the tables it lands and the questions it answers.
One connection answers questions about itself.
Two answer questions neither one can.
Shopify knows what you sold. Xero knows what it cost and what the fees were. Neither knows your actual margin by channel. Put them in the same warehouse and the question becomes answerable for the first time - and it stays answerable every night after.
Connections, answered.
What is a connection in VibeCFO?
A connection is any source EVA can read or act on. There are six kinds: purpose-built integrations into business systems, Action MCPs that reach out and change something, your own SQL databases, uploaded datasets, business documents, and public websites read on a schedule.
What is the difference between an integration and an MCP?
Direction. An integration reads data in from a system on a schedule so it can be reported on, trended and joined to other systems. An Action MCP reaches out and changes something in that system. One is about knowing, the other about doing.
Can VibeCFO connect to systems other than accounting software?
Yes, and that is the point of it. Job and practice systems, rostering, payroll, inventory, ecommerce and point of sale all have purpose-built pipelines, alongside your own databases, spreadsheets, documents and public web pages.
Do I have to connect everything at once?
No. Most people start with their ledger and one operational system, because that pair already answers questions neither could answer alone. You add the rest when a question needs them.
Where does connected data live?
In a database of your own, hosted on AWS in Sydney, not a shared tenancy. It is never used to train any model, ours or anyone else's, and it is removed from production systems within the period stated in our Terms if you leave.
What if the system I use is not supported?
Tell us and you will get a straight answer about whether it is built, in the queue, or unlikely. Some systems can be reached live over an Action MCP in the meantime, and anything with a database behind it can often be connected directly.
Connect two and see what happens.
Your ledger and one operational system already answer questions neither could answer alone. Fourteen days is enough to prove it.