Enterprise DNA

Instead of Celoxis

Stop renting Celoxis. Own your project portfolio.

We build your version around the way you approve work, review delivery and manage commitments. We map your Celoxis exports, reconcile the records and run your system through Omni by Enterprise DNA.

Celoxis Business lists US$45 per standard user per month, prepaid annually. That is US$540 per standard user a year.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The Celoxis bill

Your plan follows seats and features

Celoxis publishes standard-user plans from US$10 to US$45 per month, prepaid annually. Compare the roles and features your team uses before deciding what to replace.

paid

Standard users

Core lists US$10 per standard user per month on annual billing. Different contributor roles have separate prices.

groups

Resource planning

Essentials lists US$25 per standard user per month on annual billing and adds workload and capacity planning.

warning

Risk and intake

Professional lists US$35 per standard user per month on annual billing, with intake and risk management.

account_balance

Commercial delivery

Business lists US$45 per standard user per month on annual billing, including billing and a client portal.

extension

Connected systems

The plan comparison lists several integrations as add-ons below Enterprise. Check which connections are in your contract.

person_add

The licence mix

Celoxis states a minimum of five full-access users. Standard, contributor and read-only access are different roles.

What you own instead

A review that ends with decisions

Delivery

Find the work holding up another project

Keep original dates, revised finishes, progress and evidence together. See which predecessor is still unfinished before promising the next milestone.

  • check Milestone dates compared with the original baseline
  • check Late work and updates older than two weeks
  • check Unfinished predecessors across projects
  • check Acceptance evidence required for completed milestones

Money

Separate the budget from the request to change it

A requested change does not quietly become the new budget. A second person records the decision before its cost and date impact are counted.

  • check Base budget and approved change amounts shown separately
  • check Time cost and expenses compared with the approved budget
  • check Each project stays in its own currency
  • check Pending changes retain their requester and reason

People

See the promises made to the same person

Review weekly commitments across projects against each person’s available hours. Link the conversation to decisions and risk owners.

  • check Weekly availability set for each person
  • check Overbooked hours visible across active and proposed work
  • check Risk scores with owners and next review dates
  • check Sponsor decisions with due dates and recorded outcomes

Evidence

Keep the reason behind the status

Read the history, draft the steering pack and follow the promised benefit after delivery. Your review rules can change with your business.

  • check Dated notes and attributed record changes
  • check Branded steering packs, change requests and closure records
  • check Privacy retention reminders and checks for missing evidence
  • check Benefit owners, review dates and recorded outcomes

Make it yours

Design your own Celoxis replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Celoxis. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Celoxis replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Celoxis data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Project Portfolio for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Project Portfolio for Claude Code

Connected to your own database

What needs an owner’s attention this week?

benefit review

Project
Legacy reporting
Item
Retire spreadsheets
Owner
Mere
Due date
2026-09-12

stale update

Project
Warehouse renewal
Item
Dispatch acceptance
Owner
Aroha
Due date
2026-09-24

stale update

Project
Warehouse renewal
Item
Training sign-off
Owner
Aroha
Due date
2026-09-26

risk review

Project
Warehouse renewal
Item
Supplier acceptance delay
Owner
Aroha
Due date
2026-10-08

benefit review

Project
Warehouse renewal
Item
Reduce dispatch rework
Owner
Mere
Due date
2026-10-09

decision

Project
Customer portal
Item
Confirm pilot customer cohort
Owner
Ravi
Due date
2026-10-10

late task

Project
Warehouse renewal
Item
Dispatch acceptance
Owner
Aroha
Due date
2026-10-10

Ask it anything

Ten questions your own portfolio can answer

These questions run on the fictional demo records today. Add your own review rules as the business changes.

chat_bubble Which projects are already over their approved budget?
chat_bubble Who is committed to more hours than they have this week?
chat_bubble Which milestones slipped from their original dates?
chat_bubble Which project is waiting on unfinished work in another project?
chat_bubble Which open tasks have gone two weeks without an update?
chat_bubble What budget and date changes are waiting for a second person?
chat_bubble Which sponsor decisions are already overdue?
chat_bubble Which promised benefits are due without evidence?
chat_bubble Which risks have a high score but no recent review?
chat_bubble Which records need a retention or evidence review?

Switching

How to switch from Celoxis

A move usually starts with a one-project rehearsal, then you map and reconcile the records and run both systems side by side before retiring Celoxis.

  1. 1

    Export your project plans

    Export each project's selected Gantt columns as CSV. Include the task details you need to carry forward, since the import brings task identities, names, dates, progress, planned hours and owner text across, and retains the original columns. Dependencies, time, costs, attachments and approvals need separate reconciliation. For those records, use the export options your account allows and check with Celoxis if you are unsure what can be exported.

  2. 2

    Load one plan first

    Load a single project plan as a test run before bringing in the rest. The import brings over task identities, names, dates, progress, planned hours and owner text, while retaining original columns. Compare the task count with Celoxis and check that the records are attached to the intended project. Use a separate empty database for real work, not one containing fictional demo records.

  3. 3

    Review the test result

    Review what the test run reports before accepting the import. Check the counts and any items it identifies for attention, then compare the imported tasks with the Celoxis plan. Confirm that names, dates, progress, planned hours and owner text came through as expected. Keep a separate list of dependencies, time, costs, attachments and approvals that need reconciliation.

  4. 4

    Run both side by side

    Keep Celoxis available while you use the new records for a short period of weekly reviews. Compare the projects, dates and commitments you rely on, and check that costs, risks and decisions are represented as expected. Use this period to resolve mapping questions and decide which parts of the wider history you need to bring across before Celoxis is no longer your reference.

  5. 5

    Switch off Celoxis

    Once your team has checked the imported records, resolved the reconciliation work you need and can run its weekly review from the new database, stop maintaining both systems. Decide what Celoxis history must remain accessible, then switch off Celoxis according to your own account arrangements. Keep the new database as the place your team updates its project portfolio records.

construction

Where the real effort goes

The main work is usually mapping your own fields and rules, then deciding which history to bring across. The task import covers selected task data, but dependencies, time, costs, attachments and approvals need separate reconciliation. If Enterprise DNA runs the setup, they handle the mapping and reconciliation of the wider history, costs and attachments as part of your setup.

Not ready for a call?

Get your Celoxis switch plan by email

We will send you the step-by-step plan for moving your business off Celoxis, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose how much you want us to do

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, then npm run demo
  2. 2 Open it with Claude Code, Codex, OpenCode or Cursor
  3. 3 Try /attention and review the fictional demo records
  4. 4 Create your project and test the Celoxis CSV import before using real records
Get it on GitHub

Built around your business

We customise it

Setup scoped around your business

  • check Your project stages, approval rules and review documents
  • check Your Celoxis records mapped and reconciled
  • check A web front end or a different stack if your team needs one
  • check Your connections and team access designed with you
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and connected through Omni by Enterprise DNA
  • check Your records brought across and checked with your team
  • check Backups, access and ongoing changes operated for you
  • check One place to ask for the next improvement
Book a discovery call

Questions

Instead of Celoxis, answered

Does this replace the way we schedule in Celoxis? expand_more

The free base covers the weekly portfolio review: dates, commitments, costs, risks and decisions. It identifies unfinished predecessors and date conflicts. If your team relies on interactive scheduling, a mobile view or connected calendars, Enterprise DNA scopes those into your version before you switch.

Can we bring our existing project plans across? expand_more

Yes. Celoxis exports the selected columns from each project’s Gantt as CSV. The free import brings task identities, names, dates, progress, planned hours and owner text across, retaining the original columns. Enterprise DNA handles mapping and reconciliation of the wider history, costs and attachments as part of your setup.

Will approved changes quietly overwrite our original plan? expand_more

No. Original task finish dates remain available. A change records who requested it and why, and a second person must decide it before its effect enters the approved project budget and finish. The free base records names for attribution; Enterprise DNA sets up the team access controls your operated version needs.

Can we use our own steering pack and review rules? expand_more

Yes. The free base produces steering packs, change records and closure records with your business name, logo and colours. Enterprise DNA adapts your version to the fields, evidence and review dates your sponsors expect.

What does Enterprise DNA charge? expand_more

We agree a setup fee for your records, rules and connections, then a retainer to run and improve the system. The free version has no software licence charge. Hosting, your chosen assistant and the support you need are separate running costs.

Bring your Celoxis bill and one project review

Spend 30 minutes with Sam. We look at your licence mix, the review your team actually runs and the records you need to keep. You leave with a clear scope for your version and the work involved in switching.

Book a discovery call Get the free version

Project Portfolio for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Celoxis?

Get your version built