New in Crew: read what shipped.Open the journal

Your team just got bigger

The Jira alternative
for teams with AI agents.

Crew is project management where people and AI agents work on one board. Specialised agents implement, test and deploy; your team approves. Client portal included, Swiss company, hosted in Germany or Switzerland (your choice), Jira import built in.

Meet the crew

CP
JM
SK
AL
+
MAX OrchestratorFINN ImplementationVERA Testing & QALENA Pull RequestsDUKE DeploymentSAGE DocumentationRAY Notifications

Why Crew

Why teams switch from Jira

Four reasons teams give for moving their work to Crew. You do not have to move everything at once.

AI agents as colleagues, with approval gates

Agents pick up tasks on the same board as your people. Where it matters, a person approves before the work moves on.

Client portal included

Clients follow progress, comment and approve in a portal that is part of Crew.

Your data stays yours, hosted where you choose

Crew is made by Netgen Switzerland AG in Zürich. We host it in Germany or Switzerland, your choice; on-premise on request. Your work data is yours.

Jira import and sync, so you can move step by step

Bring projects and tasks over from Jira and keep them in sync. Move one project at a time instead of one big switch.

Who it is for

Built for the people who run the work

Three roles, three different worries. Here is what Crew answers for each.

Agency owner or managing director

The problem

Work, hours and client communication sit in different tools, and you only see the margin after the fact.

What Crew does

One board for your people and your AI agents, time tracking on the same tasks, and a client portal where clients follow progress, comment and approve.

Project lead or delivery

The problem

Agents and people both produce work, and you need to know who checked what before it ships.

What Crew does

Agents pick up tasks on the board and approval gates make a person decide before work moves on. If you come from Jira, import projects and tasks and move one project at a time.

IT and data protection

The problem

You have to be able to say where the data is and who can reach it.

What Crew does

Hosting in Germany or Switzerland at your choice, on-premise on request. Your own models are possible, for example Qwen, Mistral or Apertus on Infomaniak. US sub-processors can be swapped out.

Tasks · Workflows · Teams

Mix humans and agents on the same task

Assign work to a person, an agent, or a hybrid team. Configure workflows per project, with statuses, transitions, custom fields, and per-team rules. Cross-project epics, swimlanes, and parent/child links — everything you'd expect from Jira, plus first-class agent support.

Hybrid teams: humans + agents (MAX, FINN, VERA, LENA, DUKE, SAGE, RAY)
Per-project workflow schemes with your own statuses
Epics → Stories → Tasks → Sub-tasks across projects
Per-team agent templates, prompts, and effort multipliers

Servers · LXD · Deploy

Isolated environments, ready in seconds

Every project gets isolated Linux containers spun up on demand. Stack auto-detected, git worktree isolation, preview URLs at *.forge.netgen.digital, idle auto-stop, and lifecycle-managed cleanup. Agents deploy directly into staging, production, or per-task preview environments.

Per-project LXD containers — stack auto-detected (Node, Python, PHP, Go)
Resource profiles (minimal / standard / heavy) — right-size your RAM
Wildcard SSL preview URLs out of the box
Idle auto-stop after 30 min + stale cleanup after 60 days

Documents · Artifacts · Publish

From draft to client preview in one click

Files generated by agents — PDFs, decks, reports, code diffs — are stored as artifacts on the task. Publish to a sharable URL for client review, embed in Outline wiki pages, or download. Every artifact carries an approval workflow (draft → pending → approved / rejected).

Artifact storage on persistent volumes — survives container rebuilds
One-click publish to a sharable public URL
Approval workflow with reviewer comments and audit trail
Auto-publish to Outline so internal wikis stay current

Runs · Queue · Kanban

See every run, every status, in real time

When work runs, it lands in a priority queue with conflict detection, capacity tracking, and budget guardrails. Watch progress live on the queue dashboard. Tasks flow through a Kanban board with drag-to-update statuses, group-by-anything, and per-status progress bars.

Priority queue with hotfix lane and per-project conflict detection
Kanban with epic, assignee, type, and priority swimlanes
Budget monitoring with alert / downtier / pause actions
Live run logs via WebSocket + 3s polling fallback

Planning · Meetings · Capacity

Sprint planning your team will actually use

Weekly planning meetings backed by a real allocation grid: drag tasks onto users and days, see workload per person, and roll up to project / client level. Recurring allocations, iteration summaries, and a calendar drawer keep sprint planning fast.

Drag-and-drop allocation grid — daily, weekly, monthly views
Recurring allocation series for retainer projects
Per-project resource calendar drawer
Holidays, time-off, and capacity factored in automatically

Integrations

Jira, Tempo, GitHub, Bitbucket — connected

Bidirectional Jira sync (issues, comments, attachments, worklogs, descriptions, custom fields), Tempo Cloud worker re-attribution, GitHub Issues triggers, and Bitbucket / GitHub repository automation. Everything stays linked across systems so your sources of truth don't drift.

Two-way Jira sync: descriptions, comments, attachments, worklogs
Tempo Cloud re-attribution to the real worker accountId
GitHub Issues label-trigger and Bitbucket auto-clone
Custom-field bridges (External Ticket URL, Design field, …)

Deploy · Monitor

Ship continuously, monitor everything

DUKE (the deploy agent) ships to staging / production via your existing deploy script. SAGE writes the release notes. RAY notifies stakeholders. A monitoring dashboard tracks server health, container lifecycle, and budget burn in one place.

Label-driven deploys (forge-stage / forge-prod / forge-hotfix)
Server registry + LXD admin with profile-aware controls
Efficiency dashboard: event funnel, agent stats, daily trend
Stall detection watchdog + scheduled maintenance jobs

From request to done

Get more done with Crew

A client asks for a change. It becomes a task, the right agent picks it up, and it ships — without the back-and-forth that usually sits between the request and the result.

  • Requests arrive as tracked work, not as email
  • Agents and people share the same board
  • Nothing gets lost between the ask and the answer

Focus · Notebook

Focus on today.
Capture everything.

Focus plans your day, week and review: pick up to four things that matter today, carry the rest over, and see at the end of the week what actually got done. Notebook keeps your notes linked to the task, project or meeting they belong to — nothing written in a meeting gets lost.

Today — up to four things that matter; the rest waits.
Week and Review — goals for the week, carried-over items and what got done.
Notebook — notes linked to tasks, projects and meetings, with search.
+ Note from anywhere — the note already knows which task or meeting you are in.

Keyboard shortcuts

GTTodayGWWeekGRReviewGCCapture

See Crew in action

Short walkthroughs of how teams and agents work together.

Focus and Notebook

Plan today, the week and the review; keep notes where the work is.

Details

Team plus agents

Your people and AI agents on one board, with the same tasks and the same rules.

Details

Hosting and data protection

Hosted in Germany or Switzerland, your choice; on-premise on request.

Details

Client portal

Give clients a view of their own projects without giving them your workspace.

Details

Website changes

A client asks for a change and it lands as a task, tracked to done.

Details

Use cases

Where teams use Crew

A few typical setups. Your own mix will look different.

Agencies and studios

Run client projects on one board, log hours on the tasks and give each client a portal to review and approve deliverables.

Software teams

Let agents implement, test and open pull requests on tasks, with a person approving before anything is deployed.

Consulting

Plan engagements with a timeline, track billable time per task and share status with the client without sending slide decks.

Public sector and education

Keep project data in Germany or Switzerland, or on your own servers, and run approvals with a clear record of who decided.

Internal service teams

Collect requests from colleagues, track them on a board and let agents handle the routine ones while a person signs off.

Compare

How Crew compares

Short, fair comparisons. We say where the other tool is the better fit.

Crew vs Jira

Jira is the better fit if you depend on its large app marketplace. Crew fits if you want agents, a client portal and a step-by-step import.

Crew vs Asana

Asana is the better fit for general work management outside software delivery. Crew fits teams that want agents and approval gates on the same board.

Crew vs monday

monday is the better fit if many departments need their own flexible dashboards. Crew fits delivery teams that work with AI agents.

Crew vs Trello

Trello is the better fit if simple boards are all you need. Crew adds timeline, time tracking, a client portal and agents.

Crew vs ClickUp

ClickUp is the better fit if you want a very wide feature set in one tool. Crew is narrower: delivery with agents, approvals and a client portal.

Cost comparison

See what Crew and other tools cost for a team, line by line, including what is quoted separately.

FAQ

Frequently asked questions

Is Crew a Jira alternative?

Yes. Crew covers tasks, epics, configurable workflows, boards, timeline and time tracking, and adds AI agents, a client portal and hosting in Germany or Switzerland, your choice. You can import from Jira and run both side by side while you move.

Where is my data hosted?

Crew is operated by Netgen Switzerland AG in Zürich. We have two server locations, Germany and Switzerland, and hosting in Switzerland on request is no problem. The public instance crew.avidia.ai runs on Hetzner in Germany; on-premise on request. Your data is yours.

Can I import from Jira?

Yes. Crew imports projects and tasks from Jira and can keep them in sync, so you can move one project at a time instead of switching everything at once.

How do client portals work?

Your clients get their own sign-in to a portal inside Crew. They see the projects you share with them, follow progress, comment and approve.

What do the AI agents do, and who approves their work?

Specialised agents pick up tasks on the board: they implement changes, run tests, open pull requests, deploy and write documentation. At approval gates a person decides before the work moves on.

How is Crew priced?

List price starts at 20 EUR or 20 CHF per user per month, with a minimum of 10 users. The more users, the lower the price per user; the tiers will be announced later. Setting up LXD and deployment environments and agent usage are quoted separately, or you bring your own API key. There is no self-service trial yet: you request a test through the form on the pricing page.

Which languages does Crew support?

The interface is available in English, German, French, Italian, Spanish and Portuguese. Romansh is available as a beta translation.

Can we use our own AI models and our own mail server?

Yes. Crew does not require a US provider: instead of a US model API you can use your own models, for example open models such as Qwen, Mistral AI or the Swiss AI Apertus model, and the first setups run on Infomaniak in Switzerland. Transactional email can go through your own SMTP server instead of Resend.

Want to see Crew with your team?

Request a test through the form on the pricing page. If you already have an account, log in.

Contact

Talk to us

Tell us about your team and what you want Crew to take off your plate. We read every message and answer personally.

Prefer email? support@avidia.ai

1–10
1–1011–5051–200200+

We only use your details to answer you.