Enterprise DNA

Instead of FOSSA

Stop renting FOSSA for review records. Own your licence review desk.

We build your version around who reviews component licences, what evidence they need and how releases get signed off. We bring your FOSSA inventories across and run the review desk with you.

FOSSA Business L lists US$1,656 a month billed annually, or US$19,872 a year, for 50 contributing developers. That is its published plan price, not a customer invoice.

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

What sits inside the subscription

Separate the review records from the scanning service

FOSSA Business L lists US$19,872 a year on annual billing. Compare the review work you need with the services you use. Keep the scanning and security checks your business still depends on.

users

A contributing-developer allowance

Business L includes 50 contributing developers. Your own review records can have owners and reviewers without a licence charge for each person.

folder

Project allowances

The L selector lists 100 projects. Group your own product inventories around the way your business ships software.

layers

Release-group limits

Business L lists five release groups. Keep each release and the exact evidence used to review it in your own records.

file-text

Report configuration

FOSSA reserves its Custom licensing report flow for paid plans. Your own review packs follow your fields and approval process.

shield-check

Scanning alongside reviews

FOSSA Business includes automated licence and vulnerability scanning. This free base starts from exported inventories; your chosen scanning process remains separate.

lock

Enterprise access features

FOSSA lists single sign-on and role-based access in Enterprise. We scope shared access and reviewer permissions into the version we build for your team.

Your own working records

A release decision you can trace back to its evidence

Inventory

Know which components were reviewed

Each release keeps its imported inventory and original source document.

  • check Bring across package names, versions and licence declarations.
  • check Keep declared and concluded licences separately.
  • check Compare the component versions in two releases.
  • check Find the same package across products and see each review owner.

Evidence

Make missing evidence visible

A recorded approval needs more than a tick beside a package name.

  • check Record the actual licence and copyright text.
  • check Check applicable Apache notices and modification evidence.
  • check Keep unknown and unsupported licences waiting for specialist review.
  • check See an expired review even when an earlier approval exists.

Release review

Keep the sign-off tied to current records

Owners see the follow-ups and evidence gaps holding a release back.

  • check Assign each follow-up to a person and a due date.
  • check Block sign-off while required work stays open.
  • check Invalidate an old sign-off when a later component review changes its evidence.
  • check Flag old inventories and overdue project reviews under your house policy.

Paperwork

Prepare the release review documents

The records become documents carrying your business name and colours.

  • check Draft the attribution evidence for each release.
  • check Prepare a review pack with decisions and source references.
  • check Hand over unresolved work with its owner and deadline.
  • check Draft the weekly review from release readiness, evidence gaps and overdue work.

Make it yours

Design your own FOSSA replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your FOSSA 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 FOSSA 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 License Review for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

License Review for Claude Code

Connected to your own database

Which releases are blocked, and how much review work is left?

Harbour Dispatch

Version
1.9
Owner
Rina Patel
Target date
2026-09-21
Components
1
Blocked components
1
Open tasks
0
Readiness
blocked

Harbour Analytics

Version
1.0
Owner
Alex Chen
Target date
2026-10-29
Components
2
Blocked components
2
Open tasks
1
Readiness
blocked

Harbour Dispatch

Version
2.0
Owner
Rina Patel
Target date
2026-11-05
Components
3
Blocked components
2
Open tasks
1
Readiness
blocked

Ask it anything

Questions your own review desk answers

These questions use the records in the free demonstration. Your version can connect the same checks to your own products and review process.

chat_bubble Which releases have missing licence evidence and open follow-up work?
chat_bubble Which package appears in both products, and who owns each review?
chat_bubble Which dependency versions or licence declarations changed since the last release?
chat_bubble Which reviews have expired even though somebody approved them before?
chat_bubble Which Apache components still need their upstream notice checked?
chat_bubble Whose follow-up tasks are overdue, and by how many days?
chat_bubble Which products have passed their project review date?
chat_bubble Which inventories are too old for our release policy?
chat_bubble Who signed off a release, and do its current reviews still support that decision?
chat_bubble What review decisions and follow-up changes were recorded, and by whom?

Switching

How to move your FOSSA licence reviews

Start with one product and reconcile a real inventory before changing the wider release process.

  1. 1

    Download the inventory and licence evidence

    From the project or release group in FOSSA, open Reports and the component inventory report. Choose the supported export and keep the licensing report and original notices beside it.

  2. 2

    Bring one release into your own database

    Import its packages and preserve the original source document. Compare package counts, versions and licence declarations against your download.

  3. 3

    Complete a parallel review

    Record the evidence, named reviewers and follow-up work. Check the attribution draft against upstream files while your existing process continues.

  4. 4

    Move the agreed review workflow

    Set up private access, backups and regular inventory updates. Keep the scanning and security services you still need, with their results connected to your review desk.

construction

Where the real effort goes

A supported export can be brought into the local review desk in a day. Evidence remediation and specialist review depend on what your inventory contains.

Not ready for a call?

Get your FOSSA switch plan by email

We will send you the step-by-step plan for moving your business off FOSSA, 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

Do it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, npm test and npm run demo.
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and start with /attention.
  3. 3 Export your FOSSA inventory as SPDX JSON, test the import, then compare every package.
  4. 4 Record your evidence reviews and keep your chosen scanning process producing fresh inventories.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your product fields, review rules and approval responsibilities.
  • check Your FOSSA inventories mapped across and checked with your team.
  • check A web front end or a different stack if that suits your operation.
  • check Connections to your chosen scanning process and release workflow.
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with private access and backups set up.
  • check Review follow-ups and weekly release packs prepared for your team.
  • check Kept working as your products and review rules change.
  • check Operated through Omni by Enterprise DNA beside the rest of your business.
Book a 30-minute call

Questions

Instead of FOSSA, answered

Does this replace all of FOSSA? expand_more

It replaces the licence review desk: inventories, evidence, follow-ups and release decisions. FOSSA also supplies scanning and security analysis. Keep those capabilities through your chosen tools, and we can connect their results to your version. We agree that scope before you switch.

What does FOSSA cost for a larger team? expand_more

The Business L selector shows US$1,656 a month billed annually, equivalent to US$19,872 a year, with 50 contributing developers and 100 projects. Enterprise is quoted separately. This comparison uses the published L plan checked on 31 October 2026, not a customer invoice.

Will our existing records come across? expand_more

The free version accepts the documented FOSSA component inventory export and retains the original document. Package names, versions and licence declarations become review records. Existing vendor approvals and detailed file evidence need separate review or mapping. We check your actual export with you before relying on it.

Does a green review mean we are legally compliant? expand_more

No. It means the required evidence and dates are recorded under the configured checks. A person still verifies the original licence terms, inventory completeness and distribution obligations. Unknown or unsupported licences stay blocked, and attribution documents remain drafts for review.

Can our team have a shared screen and our own approval rules? expand_more

Yes. We build the fields, review screen, access controls and connections around your team. We can use a different stack and operate the finished system through Omni by Enterprise DNA. The commercial arrangement is one setup fee, then a retainer.

Show Sam the review work behind your FOSSA bill

In a 30-minute call, show Sam an inventory, a release review and the work your team repeats. Agree what moves into your own system, which scanning services stay and how Enterprise DNA will build and run it.

Book a 30-minute call Get the free version

License Review for Claude Code is free and open source, published by Enterprise DNA.

Done paying for FOSSA?

Get your version built