Software is a matter of trust. Especially when it does not only solve one task, but sits inside the daily work of a team.
An AI workspace sees documents, tasks, customer data, decisions, workflows and sometimes sensitive operating information. If AI agents work there too, a nice login is not enough. 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: open enough to inspect and self-host, fair enough to fund 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.
This is not an attempt to rename open source. It is 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 does not automatically make software better. AI makes context 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 does not answer every question alone. But it creates a better foundation: more insight, more operating freedom and less black box.
Why not keep it closed?
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.
We do not want teams to become even more dependent on an opaque SaaS stack. Pharen should bring workflows, knowledge, data and agents together without taking control away.
That is why self-hosting is not a side feature for us. It is a trust signal.
Why not make everything free?
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 is our attempt to hold both sides together: more control for teams and a business model that does not turn maintenance into an afterthought.
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.
At the same time, Pharen should not become an unfinished side project. 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 not a marketing phrase for us. It is the right foundation for what Pharen should become: an AI workspace that stays open enough to inspect, controllable enough for companies and fair enough for long-term operation.