Software needs trust when it sits inside the daily work of a team.
An AI workspace sees documents, tasks, customer data, decisions, workflows and sometimes sensitive operating information. When AI agents work there too, teams need to inspect how the system works, where data lives and how control remains intact.
That is why we build Pharen Hub as open fair-code. The code remains inspectable and supports self-hosting. Commercial use contributes to long-term product development.
What open fair-code means
Open fair-code connects two ideas:
- The code is open enough to inspect, understand and operate yourself.
- Commercial use contributes fairly so the product can stay maintained, secure and developed.
Open fair-code describes a deliberate position for a product that should run inside team operations.
| Model | Strength | Risk | Pharen view |
|---|---|---|---|
| Closed SaaS | Easy start, hosted operations. | Little insight, lock-in, pricing changes. | Fine for some tools, often too opaque for an AI workspace. |
| Classic open source | Visible code, community possible. | Maintenance and funding can become difficult. | Strong principle, but product operations need a sustainable model. |
| Open fair-code | Inspectable, self-hostable, fairly funded. | Needs clear communication around commercial use. | Fits a workspace that needs trust and long-term operation. |
Why this matters for AI
AI makes the context around software more important.
When an agent checks an invoice, summarizes a lead or prepares a next step, practical questions appear immediately:
- Which data does the agent access?
- Which steps are logged?
- Who may approve an action?
- Can the team control the deployment itself?
- What happens if a provider changes pricing, terms or product limits?
Open fair-code creates a better foundation through code visibility, operating freedom and a technical base teams can control.
Why open operating models matter
Closed software can be convenient. For individual tools, that is often fine. For a workspace that sits deep inside team work, data and workflows, it feels different.
Pharen brings workflows, knowledge, data and agents together while leaving teams in control of their operations.
Self-hosting is therefore part of the core operating model and a trust signal.
Why commercial use contributes
Because a workspace is not a demo repo. It needs security fixes, updates, documentation, support, migration paths, operational experience and people who can take the product seriously for years.
Open fair-code combines control for teams with a business model that funds long-term maintenance.
What this means for Pharen Hub
The Pharen Hub source code is available on GitHub. Teams can inspect how the platform is built, run their own instances and contribute to development.
An AI workspace needs maintenance, security, updates, support and product development. Fair-Code also means: when companies get real business value from it, they contribute fairly to its future.
What teams get from it
- More transparency about the technical foundation.
- More freedom between cloud, self-hosting and private setups.
- Less lock-in than fully closed SaaS products.
- A fairer cost logic than pure seat expansion.
- More trust for AI agents that touch sensitive work context.
The point
Open fair-code is the foundation for what Pharen should become: an inspectable and controllable AI workspace with fairly funded long-term operations.
