Postman adds site-wide licensing, Private Cloud, and an air-gapped client
Learn how Postman's new site-wide licensing, Private Cloud, and air-gapped client help enterprises control deployment and secure API access for agents. The post Postman adds site-wide licensing, Private Cloud, and an air-gapped client appeared first on Postman Blog .
Read the full story on Postman BlogHave you worked with this?
The story is what was announced. Nobody has discussed it yet, so if it touches your team, a short post about what you’ve seen helps the next reader.
More from Postman
Recent updates from Postman, so you can tell whether this is a one-off or part of a pattern.
How to Track Every API Your Organization Owns with API Catalog
Ask most engineering leaders how many APIs their organization runs, and you’ll get an estimate, not an answer. Teams spin up services... The post How to Track Every API Your Organization Owns with API Catalog appeared first on Postman Blog .
Postman Plugin for OpenAI Codex
Install the Postman plugin for OpenAI Codex two ways, then try the API discovery and mocking skills with real @Postman prompts. The post Postman Plugin for OpenAI Codex appeared first on Postman Blog .
From API Keys to Access Control: Rethinking Secrets Management
For as long as software has called APIs, we’ve solved the same problem the same way. The code needs a secret (a... The post From API Keys to Access Control: Rethinking Secrets Management appeared first on Postman Blog .
More in Developer Tools
What other companies in Developer Tools are doing. The category page shows who’s active, side by side.
RustRover vs VS Code + rust-analyzer: What Changes in Your Rust Workflow
As the team behind a dedicated Rust IDE, we’re naturally curious to see how RustRover stacks up against other popular setups for Rust development and the strengths and trade-offs of each one. This article is the first in a series where we’ll look at different Rust workflows. We’re not unbiased, but we want to give […]
Security Update: Multiple vulnerabilities in Next.js
The Next.js team has disclosed seven security vulnerabilities in Next.js (one high, five medium, one low), patched on September 30, 2026 in 15.5.27 and 16.3.8. The issues span server-side request forgery (SSRF), cache poisoning, and information disclosure. Several of them do not affect apps hosted on Netlify. Here's what Netlify customers need to know. Summary Some of these vulnerabilities affect…
Scale without limits: Multigres, OrioleDB, and dbarena
The app your agent built in minutes stays on the same Postgres from prototype to petabyte.
Operate with confidence
More data, more tools and more control so your agent has what it needs to observe your project, investigate issues and propose fixes, autonomously.