Chat, retrieval over your own documents, coding assistants: the applications your employees want are proven open-source products with huge communities behind them. The hard part has always been giving your people governed access to them: identity, budgets, data boundaries, updates, one support line. That is exactly what Freehold delivers. Every project below ships integrated under our app contract, working the day it lands, kept current across your fleet.
The catalog is built from the open-source products these communities have already proven, integrated under the Freehold app contract: licenses inventoried and honored, notices preserved, sign-in bridged to your identity, usage metered against budgets, and updates shipped across the fleet by us.
An enterprise chat workspace with the polish of the consumer tools: threads, agents, file uploads, and search, served in your perimeter against the models your company chose.
An open-source coding agent for VS Code and JetBrains: autocomplete, chat, and edit-in-place, pointed at your governed model endpoint.
A workspace-based retrieval product: load your documents, ask questions, and get grounded answers with citations, permissioned per workspace.
A retrieval engine built for messy enterprise paperwork: layout-aware parsing of PDFs, tables, and scans, with traceable, grounded citations.
A widely deployed self-hosted chat interface with one of the largest communities in the space and a deep plugin ecosystem.
A modern chat workspace with an agent marketplace, plugins, and strong multi-model support.
What turns a catalog of separate applications into one product: a member can start a thread in chat and pick the same context back up in the coding assistant, because every app in the deployment sits on the same governed, in-perimeter memory store.
Memory is wired once, beneath every app, instead of per-app integrations multiplying with each addition. Adding an app never silently adds a new place your data lives.
Every connector that touches member data carries the same obligations: retention limits, clean deletion when a member offboards, export on request, and no administrator back-door into member content.
Member context is held inside your boundary even when the model answering a given request is an external provider reached under your key.
Add-on applications are selected at deployment and added as your needs grow. Every app carries a publisher label, so you always know who's behind the code, and the console pairs each app with its observed adoption, so you can see which ones earn their keep.
| Publisher label | What it means | What you should expect |
|---|---|---|
| First-party | Built by Freehold, for the catalog. | We are the vendor and support path, end to end. |
| Adopted open source | A proven open-source application, integrated under the app contract. | Licenses inventoried, notices preserved, branding intact where a license requires it. We are your support-of-record and manage the upstream relationship. |
| Partner-supplied | A commercial vendor's application, integrated by us. | The vendor stands behind the code from day one; governance, deployment, and support run through us. |
| Customer-funded | An app a customer funded that entered the shared catalog. | Built once, maintained for everyone. Funding brings the app into existence, and the shared catalog keeps it maintained. |
The catalog grows with you. Need something we don't stock? We build applications that belong in the catalog for everyone, and customer-funded builds are one of the ways it grows. Every app we add is one we'll maintain for every customer after you, and that shared maintenance is what keeps yours current too.
Agent builders, pipeline canvases, and app-authoring surfaces are aimed at a technical persona most of our buyers don't employ. We put that engineering into the apps themselves instead, so what you deploy is complete.
Every app in the Freehold catalog arrives configured, governed, supported, and updated across the fleet without your team doing anything.
If you've built an AI application and your enterprise deals keep stalling on "where does our data go, can this run in our VPC, who audits usage": catalog placement solves that. We integrate your product under the app contract, and it ships with governance, cost control, and every deployment posture already answered.
The partner program →Start from the standard library and tell us what your teams need next. We'll come back with a configured deployment, ready to walk through.