Work Focal is a self-hosted platform for project tracking, team documentation, Git repositories, and integrated user management. Projects, pages, repositories, permissions, and directory-backed users operate within the same application and can reference one another directly.
Run it on infrastructure you control as a single installation or across multiple nodes as requirements grow. A hosted cloud service is not required, and the platform does not depend on a separate user-directory application simply to keep access and permissions synchronized.
Work Focal is designed to be a more stable, efficient, and security-focused alternative to conventional enterprise work-management stacks. A compiled runtime, a deliberately small dependency surface, and fewer independently operated services reduce infrastructure overhead and the compatibility chains that make large software platforms difficult to maintain.
Each capability can operate independently, while enabled capabilities share identity, administration, search, and internal references. Modular licensing enables only the functions an organization needs. Authorization remains granular: directory-backed or local groups can be combined with ACLs at the project, space, page, repository, and other resource levels.
Track issues and work items, organize backlogs and boards, plan releases, maintain roadmaps, and define workflows around the way a team actually operates.
Maintain team documentation in spaces and hierarchical pages with version history, permissions, attachments, search, and familiar wiki-style markup.
Host private Git repositories beside the work and documentation they support, with branch controls, review workflows, repository permissions, and traceable references.
User and group administration belongs to the platform itself. Multiple LDAP or Active Directory sources can be configured and synchronized from the administration interface. Synced identity is shared, while access remains granular through groups and resource-specific ACLs rather than becoming an all-or-nothing platform permission.
A work item can point to the page that defines it, the commit that changes it, and the review that approves it. Those relationships live inside the same system instead of being reconstructed through plugins and external synchronization jobs.
Projects, documentation, repositories, users, groups, and permissions are administered as parts of one platform. There is no need to maintain a second application solely to distribute the same identity information back into the first one.
Work Focal is intended for customer-controlled infrastructure. A small installation does not need to imitate a data center, while larger environments can distribute application responsibilities across multiple nodes and sites.
A straightforward deployment for smaller teams, evaluation environments, and organizations that do not need application clustering.
Add nodes for capacity, maintenance flexibility, and higher availability while retaining a single administrative platform.
Structure larger deployments around organizational and infrastructure requirements without making a vendor cloud the control plane.
Work Focal is designed to remain self-hostable. A vendor-hosted control plane is not required, and customer-controlled deployment is a permanent product model—not a temporary path toward mandatory cloud hosting. You host Work Focal on the infrastructure you choose.
This is not only about lower resource use. A smaller, more explicit software stack means fewer components that can fail, conflict during upgrades, require separate monitoring, or introduce vulnerabilities.
Work Focal is built as a compiled application without requiring a JVM, heavyweight application-server layer, or a large fleet of supporting microservices. Fewer runtime layers and dependencies mean lower resource overhead, fewer components to patch and monitor, and fewer compatibility chains that can turn routine maintenance into application work.
Operating-system and database upgrades should not require an exercise in aligning framework versions, application-server runtimes, plugin APIs, namespaces, and supporting services. Work Focal is designed to keep those external compatibility dependencies narrow and explicit so supported infrastructure can evolve without dragging a fragile application stack behind it.
Security is treated as an architectural constraint from the beginning: trust boundaries are explicit, privileges are kept narrow, input is validated deliberately, and unnecessary exposed services are avoided. The objective is to prevent classes of defects and vulnerabilities through design and review rather than accept a large attack surface as an unavoidable property of enterprise software.
Third-party components are used where they provide mature, well-tested functionality, but adding dependencies is not treated as free. Keeping the dependency surface small reduces upgrade conflicts, transitive vulnerabilities, unexpected runtime behavior, and the amount of external code that must be trusted and maintained.
The choices that reduce operational and security complexity also reduce resource requirements. Work Focal is intended to do useful application work without large memory allocations, fleets of background services, or infrastructure sized primarily to support the software stack itself.
Repository contents, project history, documentation, user data, and administrative configuration remain on infrastructure selected and operated by the customer. The application does not require a vendor cloud to function as its control plane.
Project work, knowledge, Git, and related capabilities are licensed as modules within the same application. Organizations can enable only the functions they need without operating separate server products, while identity, administration, search, linking, and granular ACL-based access remain coordinated across the deployment.