Introduction

Start here

Understand what Qodarium is, what it is being built for and the practical next step before you connect a real project.

On this page

What you are looking at

Qodarium is a self-hosted workspace for projects and long-running coding-agent sessions. It is designed to keep the conversation, working environment and repository evidence connected.

Community is the intended foundation for one developer. Team adds a planned small-team collaboration layer with shared context, handoff and review. Codex is the first runtime; model access and provider requirements are separate.

Get oriented in four steps

  1. Understand the boundary

    Read the architecture guide to see which work belongs on your machines and which supporting services may be involved.

  2. Choose a first project

    Use a non-critical repository with a clear development workflow and a focused task.

  3. Check the host

    Confirm repository access, runtime authentication, build tools and enough capacity for the real workload.

  4. Follow the release direction

    Use the roadmap to distinguish Community validation from planned Team capabilities.

Pick your next guide

Architecture

Understand the browser, workspace service, execution host and supporting service boundaries.

Host readiness

Inspect the machine and repository before depending on a browser-based workflow.

First session

Frame a bounded task, define verification and leave a useful result.

Community and Team

See the intended packaging without confusing a future collaboration feature with today's availability.

Continue from here

Read the architecture guide, work through host readiness, then use the first-session workflow.

For project announcements, follow Qodarium on Threads or subscribe to the journal feed.

A little less watching. A lot more building.

Make room for
long-running ideas.

A workspace that holds the context while you focus on what comes next.

IN DEVELOPMENT · COMMUNITY + TEAM