Enterprise DNA

Instead of Port

Stop renting Port. Own your service catalog.

We build your version around how your team owns and reviews software, bring your Port catalog records across, and run it for you through Omni by Enterprise DNA.

Port Basic starts at $30 per seat per month, billed annually, in a 50-seat package. The vendor displays dollars without naming the currency.

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 you pay for

A platform subscription around your service knowledge

Port combines a catalog, standards checks and workflow features. If your immediate job is ownership and evidence review, start with those records and build around your process.

paid

A package of seats

Basic starts at $30 per seat per month on annual billing, sold as a 50-seat package.

group

A higher starting rate as the plan grows

Standard starts at $40 per seat per month and covers up to 200 seats.

storage

Catalog capacity by plan

Basic lists 50,000 entities. Standard lists 250,000. Your catalog size is part of the subscription choice.

dashboard

Shared workspaces

Standard lists up to five workspaces for organising the platform.

lock

Access features by tier

Single sign-on appears in Standard. Enterprise adds further account controls under custom pricing.

support_agent

Hosted support

Paid plans include commercial support. The free tier offers community support for teams evaluating the platform.

What you own

The service review your team actually needs

Ownership

A named team and a recent review

Find unowned services and old ownership reviews before the next handover.

  • check One responsible team for each service
  • check Review dates alongside service importance
  • check A combined view of overdue ownership and open remediation
  • check A branded handover with the current evidence and next work

Standards

Know what passed and what is only recorded

Evidence dates, results and exceptions stay separate. An old pass becomes stale when its agreed review period ends.

  • check Passed, failed, missing and stale evidence shown separately
  • check An evidence reference and operator recorded for each assessment
  • check Exceptions retain their reason, approver and expiry
  • check A failed check stays visible even while its exception is current

Dependencies

See the risks recorded between services

Review direct dependencies alongside ownership and standards gaps in the same database.

  • check Services that depend on deprecated or retired components
  • check Dependencies with no responsible team
  • check Dependent services whose standards evidence needs review
  • check Retirement refused while active dependent services remain

Weekly work

Turn gaps into assigned follow-up

The Monday review joins ownership, dependencies and outstanding work. Each task has an owner, due date and recorded resolution.

  • check Overdue remediation beside the service it affects
  • check Upcoming and expired exceptions in one review
  • check Local handover and weekly review drafts
  • check Original import records retained beside subsequent changes

Make it yours

Design your own Port replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Service Catalog for Claude Code

Connected to your own database

Which services need an ownership review?

catalog

Name
Product Catalog
Team
UNASSIGNED

checkout

Name
Checkout API
Team
commerce
Reviewed_on
2026-07-09

checkout-worker

Name
Checkout Worker
Team
UNASSIGNED

legacy-tax

Name
Legacy Tax Adapter
Team
UNASSIGNED
Reviewed_on
2026-06-09

Ask it anything

Ten questions your service records can answer

These are included questions answered by this build. Port also supports custom reporting; we make no claim that the same questions are impossible there.

chat_bubble Which critical services lack a responsible team?
chat_bubble Which production services depend directly on deprecated or retired services?
chat_bubble Which services have stale evidence despite a recorded pass?
chat_bubble Which standards have never been assessed for each service?
chat_bubble Which exceptions expired while their checks still failed or lacked evidence?
chat_bubble Which teams own services with overdue remediation?
chat_bubble Which services have an exception but still lack a runbook?
chat_bubble Which production services have no dependency records?
chat_bubble Which imported services still await an ownership review?
chat_bubble Which services combine overdue ownership reviews with open remediation?

Switching

How to switch from Port

A move involves exporting your catalog, mapping its fields and teams, checking the import, and confirming your day-to-day work in the new catalog before you switch off Port.

  1. 1

    Export your catalog

    Start with Port’s catalog CSV export. Make the identifiers and columns you need visible before exporting, because the export contains visible columns and entities permitted by your current filters. If your account does not offer the fields or records you need, check with Port. Keep a copy of the export while you confirm which custom fields and history you want to bring across.

  2. 2

    Map and test the import

    Map the exported columns to catalog fields and match services to existing teams, then run a test import before loading records. The test checks the import without keeping its changes. Review the results with someone who knows your Port records, especially services that did not match a team. Use the same source label for this Port catalog each time you import it.

  3. 3

    Review flagged records

    Check the import results before completing the load. Unchanged duplicates from the same source are skipped, while changed records are rejected for reconciliation. A bad row rolls back the full batch, so resolve issues before trying again. Reconcile the imported record count against Port. Custom fields stay in each service’s original source row, so confirm that you can find the information your team needs.

  4. 4

    Run both side by side

    Keep Port available for a short period while your team uses the new catalog. Compare service ownership, direct dependencies, recorded evidence and open work against Port, and follow up on gaps. Imported owner reviews are not assumed complete. Dependencies and assessment history need separate mapping, so check that the records your team relies on are present before making the new catalog its working record.

  5. 5

    Switch off Port

    When your team is satisfied with the records and its process in the new catalog, make it the working record and switch off Port under your account and contract arrangements. Check first whether you rely on other parts of Port, such as integrations, developer self-service, sign-in, a public portal, provisioning or live resource discovery. Those are outside the base catalog and need separate scoping if you still need them.

construction

Where the real effort goes

The real work is usually mapping your own fields and rules, then deciding which history to bring. Dependencies, assessment history and permissions need separate mapping, and custom fields stay in the original source row. If you have Enterprise DNA run the move, they handle this mapping and migration as part of the scoped work.

Not ready for a call?

Get your Port switch plan by email

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

Do it yourself, make it yours, or have us run it

Open source

Do it yourself

Free MIT code

  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
  3. 3 Export the Port catalog as CSV, map its visible columns and preview the import
  4. 4 Record your teams, evidence and dependencies, then render the weekly review
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your fields, ownership rules and standards
  • check Your Port export mapped and reconciled
  • check A web front end where your team needs one
  • check A different technology stack when it suits your business
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated inside Omni by Enterprise DNA
  • check Your catalog records brought across and reviewed
  • check Agreed connections to your existing systems
  • check Backups, access controls and ongoing support scoped for your team
Book a call with Sam

Questions

Instead of Port, answered

Does this replace every part of Port? expand_more

The free version covers the internal catalog desk: ownership, direct dependencies, recorded evidence, exceptions and follow-up work. Port is a broader hosted platform. We agree the connections, access controls and any self-service screens your team needs as part of your custom version.

Can we bring our Port records across? expand_more

Yes. Export the service catalog as CSV with the identifiers and columns you need visible. The import maps those columns and matches existing teams, with a test run first. Original rows remain with each service. Dependencies, assessment history and permissions need separate mapping; we scope that with you.

Does a passing standards check prove compliance? expand_more

No. It records an assessment and its evidence date. Selected checks support NIST software security practices, but they do not inspect your software or certify compliance. The evidence, reviewer and exception decision remain your responsibility.

What happens when a team changes or an exception expires? expand_more

Assign the new team and make a fresh ownership review. Expired exceptions appear in the attention list and stop suppressing the related gap. A completed task needs a resolution note, so the next owner can see what happened.

What do we pay Enterprise DNA for? expand_more

You can install and operate the free version yourself. We charge one setup fee, then a retainer to build your version, bring your records across, connect the agreed systems and look after it. The scope follows your team and the parts of Port you use.

Know who owns the service and what still needs attention

Spend 30 minutes with Sam. Bring your Port bill and one service review. We will work through the records, connections and operating support your own version needs.

Book a call with Sam Get the free version

Service Catalog for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Port?

Get your version built