Software Holdings
The same reporting system built in four companies is one entry in the graph, with all four named.
Each acquisition arrives with its own repositories, its own vocabulary and its own version of authentication, billing and reporting. Foundariq reads every company's code into one capability graph, keyed by what each capability does rather than by what its company happened to call it. Where consolidation pays, a shared capability can be promoted; where it does not, nothing moves. Each company keeps its own Blueprints, policies and approval rules throughout.
I approve four engineering budgets that each contain a line for reporting. Nobody can tell me whether that is four different problems or one problem I am paying for four times.
Duplication becomes a list, not a hunch
Every company's repositories map into one capability graph, and the graph marks where a capability exists more than once. Each entry names the companies carrying a copy, the budget line each of them is funding for it, and the version a shared capability would start from. Consolidation becomes something you can price rather than something you suspect.
One library, separate governance
Companies draw on the same capability library while keeping their own Blueprints, policy profiles, approval rules and repositories. A rule set at holding level is evaluated everywhere. A rule that belongs to one company stays inside it.
Due diligence starts with a scan
Point Foundariq at a target's repositories and it returns their products, entities, capabilities and the overlap with what you already own. That happens before anyone has learned the codebase, and it is derived from the code rather than from what the seller wrote down.
Provenance in one shape everywhere
Each release ties to a Blueprint version, a generator version, capability versions, a policy profile and lock files, in the same format for every company in the group. One audit question gets one answer shape, whichever company it lands on.
What changes
Foundariq for Software Holdings
Blueprints
The Blueprint records what your software means before any file is generated, and a published version of it is what every release points back to.
5 capabilitiesCapability Graph
The portfolio as a library: every capability with a key, a version, an owner, a status and the products depending on it.
5 capabilitiesGovernance
Deterministic checks run first, policy decides second, and every proposal, review, approval and publish stays on the record.
5 capabilitiesOther solutions
Built for who is asking.
Founders
State it once in the Blueprint, and every agent after that reads it instead of asking you again.
SaaS
A third way to do authorisation never gets built, because the policy profile refuses the proposal.
Venture Studios
Product ten opens with a search across the nine before it, and builds only what comes back missing.
Software Holdings
One capability graph across companies that share no repositories, with every duplicate attached to the companies paying for it.
Agencies
The client inherits a Blueprint they can read, not a repository one developer understands.
Enterprise
Every autonomous change names who proposed it, which rule cleared it and which person approved it.
Stop managing prompts. Start managing software strategy.
Connect your repositories. Let Foundariq understand what you have already built. Then tell it what your portfolio should build next.
Read-only to start · Your code stays in your GitHub · [email protected]