Frequently Asked Questions

OpenArca is an open-source, self-hosted execution workflow designed for developer teams. It combines issue tracking, Kanban workflow, developer TODO execution, and workflow context preservation. The main goal is to reduce execution friction and prevent loss of context between tickets and real development work.

Yes. OpenArca is designed as a lightweight alternative to complex project management tools like Jira, especially for small and medium developer teams. Instead of focusing on enterprise planning, OpenArca focuses on execution clarity, developer workflow, and context continuity.

Traditional issue trackers mainly store issues. OpenArca connects issues directly with developer execution tasks, workflow state transitions, and contextual history. This reduces the gap between tracking work and actually doing it.

Execution Memory is the idea that teams should not lose context while work moves. OpenArca preserves decisions, ownership, workflow history, and execution flow so developers can continue work without losing understanding.

Yes. OpenArca is designed to be self-hosted. Teams can run it using Docker and keep full control over data, infrastructure, and workflow customization.

Yes. OpenArca is released under the AGPL-3.0 license. You can use and modify it freely. Companies can self-host it internally. Improvements shared over network usage must remain open.

Yes. Companies can deploy OpenArca inside their organization and use it for internal workflows without restrictions. AGPL mainly applies when software is modified and offered as a network service.

Yes. OpenArca is built with AI-era development workflows in mind. As AI agents accelerate coding, teams need structured workflow context, clear ownership, and stable execution states. OpenArca helps preserve that structure.

Not necessarily. OpenArca focuses on execution workflow. Some teams use it as their primary system, while others use it alongside higher-level planning tools.

OpenArca works best for small and medium developer teams, internal IT teams, engineering-focused startups, teams experimenting with AI coding workflows, and organizations preferring self-hosted solutions.

Many teams lose context between support tickets, development tasks, and workflow handoffs. OpenArca connects these layers so execution remains clear throughout the entire development cycle.

Passwordless authentication simplifies onboarding, reduces friction for internal users, and improves usability for support-driven workflows. Users receive a secure 8-digit code via email, valid for 10 minutes.

Yes. Being open source and self-hosted means teams can adapt workflow logic, extend functionality, and integrate with internal tools.

OpenArca is primarily optimized for small and mid-sized engineering teams that prefer lightweight execution workflows. Large enterprises with complex governance may require additional layers, which are planned as part of the Enterprise edition.

OpenArca includes developer TODO synchronization, Kanban integration, and execution-focused workflow states. Developers can operate from a focused execution view instead of managing tickets manually.

OpenArca was created to solve a common problem: teams don't lose tasks — they lose execution context. The project aims to keep that context alive while work moves forward.