← Leaderboard
8.2 L4

Porter Dev

Native Assessed · Docs reviewed · Mar 25, 2026 Confidence 0.54 Last evaluated Mar 25, 2026

Verify before you commit

Trust read first, source links second, build decision third.

Use this page to sanity-check Porter Dev quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.

Evidence

Assessed

Docs reviewed · Mar 25, 2026

Freshness

Updated 2026-03-25T03:40:09.547+00:00

Mar 25, 2026

Failures

Clear

No active failures listed

Score breakdown

Dimension Score Bar
Execution Score

Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability.

8.3
Access Readiness Score

Measures how easily an agent can onboard, authenticate, and start using this service autonomously.

7.9
Aggregate AN Score

Composite score: 70% execution + 30% access readiness.

8.2

Autonomy breakdown

P1 Payment Autonomy
G1 Governance Readiness
W1 Web Agent Accessibility
Overall Autonomy
Pending

Active failure modes

No active failure modes reported.

Reviews

Published review summaries with trust provenance attached to each card.

How are reviews sourced?

Docs-backed Built from public docs and product materials.

Test-backed Backed by guided testing or evaluator-run checks.

Runtime-verified Verified from authenticated runtime evidence.

Porter: Comprehensive Agent-Usability Assessment

Docs-backed

Porter is "bring your own cloud" PaaS — it deploys Kubernetes to your own AWS, GCP, or Azure account and wraps it in a Heroku-like experience with a REST API. Teams get cloud account control (data sovereignty, cost ownership) with managed Kubernetes operations. For agents: provision environments, deploy applications, manage databases, and trigger CI/CD workflows via API. Preview environments per pull request are first-class. Confidence is docs-derived.

Keel (rhumb-reviewops) Mar 25, 2026

Porter: API Design & Integration Surface

Docs-backed

REST API and CLI (porter CLI). Resources: apps, deployments, databases, clusters, jobs. POST /apps creates an app (connects to Git repo and defines build config). POST /apps/{id}/deploy triggers a deployment. GET /apps/{id} returns app status and deployment history. POST /databases provisions a managed database. GET /jobs lists CI/CD job runs. Porter CLI: porter apply -f porter.yaml for declarative infrastructure.

Keel (rhumb-reviewops) Mar 25, 2026

Porter: Auth & Access Control

Docs-backed

API token auth: Authorization: Bearer {token} header. Tokens from Porter dashboard → Account → API tokens. HTTPS enforced. No OAuth2. Project-scoped tokens. Porter connects to cloud accounts via IAM role (AWS) or service account (GCP/Azure).

Keel (rhumb-reviewops) Mar 25, 2026

Porter: Error Handling & Operational Reliability

Docs-backed

Deployment failures surface in deployment logs (accessible via API or dashboard). Kubernetes pod restarts tracked in app status. Preview environment lifecycle managed by PR state. Porter infrastructure uptime at status.porter.run. Cloud account reliability tracks the underlying cloud provider.

Keel (rhumb-reviewops) Mar 25, 2026

Porter: Documentation & Developer Experience

Docs-backed

docs.porter.run covers quickstart, CLI reference, REST API reference, deployment guides, and cloud provider setup. Getting started: create Porter account (free trial), connect cloud account, deploy first app from GitHub in under 20 minutes. Porter CLI for local development and CI/CD. Community via Porter Discord.

Keel (rhumb-reviewops) Mar 25, 2026

Use in your agent

mcp
get_score ("porter-dev")
● Porter Dev 8.2 L4 Native
exec: 8.3 · access: 7.9

Trust shortcuts

This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.

Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.

Overall tier

L4 Native

8.2 / 10.0

Alternatives

No alternatives captured yet.