How a buyer can evaluate the product
The Free plan supports up to 15 seats, 10,000 entities and 400 to 500 automation runs (the pricing page shows both figures), which is enough to test one catalog model and a small set of actions with public docs.
Production requirements include source integrations, entity blueprints, relationship ownership, access policy, workflow credentials, scorecard governance, action failure handling, usage capacity and support.
Public pricing lists Free, Basic from $30 per seat monthly billed annually, Standard from $40, and custom Enterprise with a platform fee plus seats. Enterprise adds scale, private networking, identity, flexible deployment, SLA and support controls.
Sources: Port pricing · Port documentation · Port software catalog
Evidence a buyer can inspect
| Buyer question | Public evidence | How to use it | Source |
|---|---|---|---|
| What is cataloged? | Blueprints define entities, properties and relationships in the software catalog. | Model services, owners, environments and dependencies. | Catalog docs |
| How do developers act? | Self-service actions trigger automations and integrations. | Inspect credentials, approvals, logs and rollback. | Actions docs |
| How is quality measured? | Scorecards evaluate catalog entities against rules. | Assign rule owner, data source and remediation path. | Scorecard docs |
| What creates plan pressure? | Seats, entities, automation runs and enterprise controls differ by tier. | Forecast each capacity and required control. | Pricing |
Sources: Port pricing · Port documentation · Port software catalog · Port security
How to use this in your own materials
An internal developer portal is explained well when every visible catalog fact has a source and owner, and every action has an authorization and failure path. The portal screenshot is secondary to whether those data and operating responsibilities are credible.
Method and limits
We read the listed first-party pages on 2026-09-08 and compared them with our notes from a July 2026 review. We looked at what a technical buyer can verify before contacting sales. We did not test the product or check customer results the vendor reports.
- We did not deploy Port or validate integration freshness.
- Starting prices exclude potential platform fees, add-ons and negotiated terms.
- Vendor customer stories were not treated as independent performance evidence.
Sources: Port pricing · Port documentation · Port software catalog · Port security
Sources and dates
- Port pricing ↗Reviewed 2026-09-08
- Port documentation ↗Reviewed 2026-09-08
- Port software catalog ↗Reviewed 2026-09-08
- Port security ↗Reviewed 2026-09-08
Found an error or a changed source? Send a correction.
Apply this to your company
Draft your next buyer document from approved claims.
Briefs and decks from approved facts, every claim sourced.
See the demo →