A1 ratingsProgress SoftwareChef Opsmith

Chef Opsmith
Progress Software · agent · Any industry Early access
-Grade
-Score
±1695% range
-Rank of 1134
0%From fleets
FR-CAT-01371Catalog no.
In beta or announced. A1 shows the facts but grades only released products, so early numbers never follow a product into release.
The six pillars
Each bar is the score; the bracket is its 95% range.
Can you see what it costs?
Nothing a buyer can read · prices on request only
Desk research 0 · counts for 25% · A cost API you can call scores highest; an admin console or cloud billing export next; a card statement or emailed invoice is all some products leave you. Published prices add to it.
Can you see how much it's used?
No usage API found
Desk research 0 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.
Can you tie cost to one agent?
Nothing a buyer can read
Desk research 0 · counts for 15% · Exact (one key or project per agent) beats by-project, by-workspace or by-user.
Can an agent on it report out?
Not known yet. Sits at a neutral 50 with a wide range until facts arrive · counts for 15% · A remote MCP connector scores highest, then a local MCP server, an SDK, an API or a workflow step; copy-and-paste lowest. Any open standard counts, not just FleetRegistry.
Can you control spend and access?
Per-agent keys: Not scoped · Audit log: By API · Revoke: Console only · SSO: SSO only
Desk research 75 · counts for 20% · Hard spend caps (30%), scoped per-agent keys (25%), an audit log you can read by API (20%), revoking by API (15%), SSO with SCIM (10%).
Does it work on small plans?
Small plans don't get the data
Desk research 0 · counts for 10% · Whether the plan a person or small business buys gets the cost and usage data at all.
Where the evidence comes from
Independent fleets0%Desk research52%Neutral starting point47%
Once three independent fleets report on a pillar, desk research counts for at most a third of it. FleetRegistry's own fleets never count.
Controls on record
Spend capNot known
Per-agent keysNot scoped
Audit logBy API
RevokeConsole only
SSOSSO only
PricesOn request
Controls documented for the Chef 360 platform that hosts Opsmith, not Opsmith itself: API tokens (default 30-day expiry) are created, revoked and deleted via the platform CLI (no UI steps documented) and take the creating user's role; audit logs via REST GET /api/log-service/audit/admin and /self (max 10 days per request); SAML 2.0/OIDC SSO with invite-only provisioning, SCIM not mentioned. No spend cap documented.
History
11-12 - 11-13 - 11-14 - 11-15 - 11-16 - 11-17 - 11-18 - 11-19 -
Not saved yet. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-04.Run agents on Chef Opsmith?
Give each one a permanent number, a named person who answers for it, and a record of what it can touch and what it costs. Free.