NewCore vs Obot
| Criterion | NewCore | Obot | NewCore reason | Obot reason |
|---|---|---|---|---|
| G1 Identity-bound per-call authorization (25) | 10 | 5 | Every tool call passes through the gateway, which identifies the agent and the person behind it and checks the action against policy, keeping agents within that person's permissions. [nc-secure] | Access to MCP servers is granted per user and group, but per-call checks against the person an agent acts for are not described. [obot-gh] |
| G2 Credential brokering (20) | 10 | 5 | Access is short-lived and task-scoped, and the agent never holds the tool's own credential. [nc-secure] | The platform stores and manages server credentials, but short-lived token brokering was not described. [obot-gh] |
| G3 Human approval and escalation (15) | 10 | 2 | Policies return allow, ask or deny; risky calls go to a named approver who confirms with device biometrics, and an agent can never approve its own action. [nc-govern] | No human approval step for tool calls was found. [obot-gh] |
| G4 Server registry and discovery (10) | 8 | 8 | A connection registry records each MCP server's endpoint, owner and environment, and agents are found through read-only integrations without relying on registration. [nc-secure][nc-discover] | A catalog of approved MCP servers is managed centrally, and the Obot CLI lets users discover and install them. [obot-gh] |
| G5 Audit evidence (10) | 9 | 6 | Tool calls, sessions and approvals sit in one audit trail with each call logged against its owner; a SIEM export was not named on the pages read. [nc-govern] | Audit logs record findings, and egress audit logging adds auditor-only views; SIEM export was not confirmed. [obot-gh] |
| G6 Standards (10) | 5 | 4 | MCP, SAML and OIDC are named; OAuth 2.1 and Enterprise-Managed Authorization are not named on the pages read. [nc-foundation] | OAuth is used for server connections, but specific MCP authorization standards were not named. [obot-gh] |
| G7 Deployment and buying clarity (10) | 4 | 9 | Delivered as SaaS with no list price; an AWS Marketplace listing exists and no free tier or self-host option was found. [nc-aws] | Every edition runs the same MIT open source code, so self-hosting is free. [obot-gh] |
| Total | 8.60 | 5.25 | Weighted sum divided by 100. | |
In short: NewCore totals 8.60 and Obot totals 5.25 on our weighted rubric, a gap of 3.35 points. NewCore is ahead on per-call authorization, credential brokering, human approval, audit and standards. Obot is ahead on deployment. Choose by the criteria your agents depend on, then check deployment and pricing below.
Which one should I choose?
NewCore totals 8.60 against 5.25 for Obot. The largest weighted difference is on per-call authorization. Obot is ahead on deployment.
Pick NewCore if per-call authorization matters most to you.
It scores 10 against 5 there: every tool call passes through the gateway, which identifies the agent and the person behind it and checks the action against policy, keeping agents within that person's permissions.
Pick Obot if deployment matters most to you.
It scores 9 against 4 there: every edition runs the same MIT open source code, so self-hosting is free.
How do deployment and pricing compare?
| Parameter | NewCore | Obot |
|---|---|---|
| Deployment | SaaS. Works alongside an existing AI gateway, and the current identity platform keeps handling employee sign-in. | Self-hosted container image; same code in every edition. |
| Price as published | No list price published. Listed on AWS Marketplace. | Free under the MIT licence; Enterprise edition terms not published on the page read. |
| Identity provider | Yes. NewCore says to start alongside your identity platform, which keeps handling employee sign-in while NewCore governs agent access. | Partly. Obot supports sign-in through external providers, but details were not confirmed on the page read. |
Full datasheets: NewCore and Obot MCP Gateway.
Frequently asked questions
- Which is better, NewCore or Obot?
- On our rubric NewCore totals 8.60 against 5.25 for Obot. The better choice depends on which criteria matter most to you.
- Do NewCore and Obot work with my identity provider?
- NewCore: Yes. NewCore says to start alongside your identity platform, which keeps handling employee sign-in while NewCore governs agent access. Obot: Partly. Obot supports sign-in through external providers, but details were not confirmed on the page read.
- How do NewCore and Obot differ on price?
- NewCore: No list price published. Listed on AWS Marketplace. Obot: Free under the MIT licence; Enterprise edition terms not published on the page read.
By The Datasheet desk · Published and reviewed 2026-11-03