QodariumCommunity & Team
A personal self-hosted foundation first. A planned collaboration layer for small teams, with deliberate boundaries around what belongs in each package.
On this page
Community: the personal foundation
The intended Community package is free for one developer and centers on projects, repositories, local and remote hosts, Codex sessions and retained working context.
The scope includes files, terminal, diffs, worktrees, approvals, project instructions and a basic operational foundation. Availability is determined by release validation, not by a marketing checklist.
Team: the intended collaboration layer
Shared projects and history
Give team members a common context for the work and the sessions behind it.
Handoff packages
Move a task with its goal, changed surface, evidence, open questions and next step.
Explicit review
Use Accepted and Changes requested decisions to close the feedback loop.
Remote and operational services
PWA, relay, push, managed updates and support are part of the intended Team direction.
Small teams, intentionally
The initial Team validation scope is up to five people with an owner/member model. Enterprise roles, SSO, SCIM and elaborate permission matrices are not part of that first scope.
The product is not a replacement for Git, a full project-management platform or a production deployment orchestrator.
Availability and pricing
Community and Team are product directions under development. This preview website does not offer a paid checkout, a guaranteed launch date or a generally available Team subscription.
Pricing is still being validated. The public package and commercial terms should be read from a versioned launch announcement when they are available.
A few good questions
Are all described features ready now?
No. Preview and Planned labels distinguish intended capabilities from released availability.
Is model usage included?
Do not assume so. Agent authentication, provider plans and usage limits are separate concerns.
Is Claude Code supported?
Codex is first. Additional integrations require their own release gate and are not advertised as stable here.
Follow the sequence
Read the roadmap for the order in which the product is being validated.