Which fits: Postman or self-hosted Hoppscotch?
Most readers arrive here after Postman's March 2026 plan change, which limited the Free plan to one user who cannot create a team, or after a data residency or lock-in review that asks where collections and credentials sit. The decision is about where your team's shared workspaces live and who is responsible for running them. Postman fits teams that are comfortable with cloud collaboration, want the vendor to operate the service, and value a single supported product with a broad feature set. Self-hosted Hoppscotch Community Edition fits teams that need shared workspaces on infrastructure they control, with the collections held in a PostgreSQL database reached through the DATABASE_URL setting on servers inside your own network or cloud accounts.
Before you choose, confirm four things with your own environment and your vendor. First, sign-in: Community Edition signs users in through Email, GitHub, Google and Microsoft OAuth providers that an administrator configures, and it needs SMTP settings for email, so check whether those identity sources satisfy your policy. Second, SSO and SCIM: Hoppscotch's SAML, OpenID Connect and SCIM provisioning sit in the paid Enterprise Edition, which requires a license key, so if automated user and group provisioning is mandatory, price that edition into the comparison. Third, CI use: if pipelines depend on Newman or the Postman CLI, confirm that the Hoppscotch CLI, which is still labeled alpha, covers your test cases and reporting needs. Fourth, staff: someone must install, administer, back up and upgrade the server, and Community Edition support comes from the community forum rather than a contract.
Which option fits which scenario
This table matches four common situations to the option that fits best and the condition that makes it so. Read each row against your own constraints, then confirm the condition with the vendor or in a pilot before committing.
| Scenario | Better fit | Condition that makes it the fit |
|---|---|---|
| Small team that lost shared collaboration on the Free plan | Hoppscotch Community Edition or Bruno | Hoppscotch fits if the team wants shared workspaces on a server it runs. Bruno fits if the team is comfortable keeping collections as files in Git and does not need live shared workspaces. |
| Team that wants to stay on Postman's cloud | Postman Team plan | Choose this only if the team accepts cloud-hosted collections and the seat cost. Confirm current seat pricing and add-on terms with Postman, since the plan structure changed in March 2026. |
| EU or air-gapped team that cannot send collections to a vendor cloud | Bruno (offline) or self-hosted Hoppscotch | Bruno fits when single-user or Git-based work is enough and no sign-in is wanted. Hoppscotch fits when the team needs shared workspaces, and the server sits in an EU or isolated network the organization controls. |
| Team that needs SAML SSO and SCIM provisioning on its own servers | Hoppscotch Enterprise Edition | Required when SCIM user and group provisioning is mandatory. Community Edition covers OAuth sign-in, not SCIM. Bruno's paid editions also list SAML SSO and SCIM, so compare license terms and deployment models with both vendors. |
| Team that runs collections in CI pipelines | Bruno CLI or Hoppscotch CLI | Bruno fits when collections already live in Git and bru run with test reports is enough. Hoppscotch fits when the team wants hopp test with JUnit XML reports and a shared instance as the source. The Hoppscotch CLI is marked alpha, so pilot it before relying on it. |
| Team with existing Postman collections and environments to move | Hoppscotch or Bruno importer | Both import Postman collections. Hoppscotch's self-hosted import limit is 50 MB, so check export size first. Scripts usually need rewriting in either tool. |
| Team that needs a fully offline client with no account | Bruno | Fits when no shared server is required. Postman requires a signed-in account for collections, and the offline Scratch Pad was retired in 2023. |
Where collections live and who controls the data
Each API client stores collections somewhere different, and that location decides who can read credentials, who signs users in and what evidence you can produce. The cards below walk through Postman's cloud model, the EU instance limits and the components a self-hosted Hoppscotch server needs.
Postman cloud storage
Postman keeps shared collections, environments and team workspaces in its cloud, and collections require a signed-in Postman account. The offline Scratch Pad mode was retired in 2023, so there is no fully local mode to fall back on. Before a move, export what you need and confirm with Postman which data, including embedded tokens in environments, sits in its cloud today.
EU Frankfurt instance limits
Postman's EU Data Residency instance in Frankfurt is available only to Enterprise customers. If your concern is EU storage for smaller teams, that option is not open to you without an Enterprise contract. Ask Postman to confirm in writing which features the EU instance excludes and which data categories it covers.
Self-hosted Hoppscotch server
Hoppscotch Community Edition is packaged as Docker containers, with separate frontend, backend and admin images or a single all-in-one container, and a Helm chart for Kubernetes. Your team installs, administers and updates it, so the server, its logs and its backups sit inside your own infrastructure. Confirm which image layout and update cadence fits your change process.
PostgreSQL as the system of record
Hoppscotch Community Edition stores team workspace data in PostgreSQL, set through DATABASE_URL. This database becomes the place where collections, environments and any stored credentials live, so it needs the same encryption, access control, backup and restore testing as your other production databases. Ask your DBA to confirm the database tier and retention before you import anything.
Identity, OAuth providers and SMTP
Hoppscotch Community Edition signs users in through Email, GitHub, Google and Microsoft OAuth providers that the administrator configures, and it needs SMTP settings for email. Each provider you enable becomes a dependency for access, and the mail relay becomes part of the sign-in path. Decide which identity source is authoritative for your users and who can reset accounts.
Compliance evidence is yours to produce
A self-hosted instance moves the evidence trail to your side: access logs, configuration baselines, backup records and change history. DeployOpen can plan, configure and document these controls and prepare evidence for a compliance assessment, but it does not issue audit reports or attestations. Independent auditors and certification bodies perform that assessment, so agree the evidence list with them early.
How a self-hosted Hoppscotch instance is built
A self-hosted Hoppscotch Community Edition instance is packaged as Docker containers. You can run separate frontend, backend and admin images, or a single all-in-one container. The documentation also provides a Helm chart deployment guide for Kubernetes, so the choice depends on whether your platform team already operates a container runtime or a cluster. The database connection is set once through `DATABASE_URL`, which points the backend at a PostgreSQL database you control. Team workspaces, collections and environments are stored there, so the database needs the same backup, access control and retention rules you apply to other systems holding API credentials.
Build resources are a separate planning item. The prerequisites page lists 4 CPU cores and 4 GB of RAM to generate the build image, and as little as 1 CPU core and 2 GB of RAM to host the built output. Confirm these figures against the current prerequisites page before sizing hosts, because they change between releases and your container platform, database and reverse proxy add their own load. Also check the install and build steps for the version you plan to deploy, since the build and hosting steps may run on different machines.
Users sign in through Email, GitHub, Google or Microsoft OAuth providers, and the administrator enables and configures each one. Email sign-in needs SMTP settings, so your mail relay, sender address and TLS requirements must be settled before go-live. Decide which providers match your identity landscape, register the redirect URLs for your instance hostname, and test each sign-in path with a pilot group. Hoppscotch Enterprise Edition adds SAML and SCIM for centralized provisioning, but the Community Edition does not, so confirm whether manual account management is acceptable for your team size.
When is the paid Enterprise Edition needed?
Is Hoppscotch Community Edition free to use in a company?
Yes. Hoppscotch is licensed under the MIT License, and its self-hosting documentation states that the Community Edition is free, open source and usable for personal and commercial projects. The cost you carry is the infrastructure you run it on, the PostgreSQL database behind it, and the staff time to install, administer and upgrade it. Community Edition releases arrive quarterly, and support comes from the community forum rather than a contract. Confirm the current license terms in the repository's LICENSE file before rollout, since terms can change between versions.
Which teams can stay on Community Edition without SSO or SCIM?
Teams without a written mandate for centralized sign-in or automated user lifecycle management usually can. Community Edition signs users in through Email, GitHub, Google and Microsoft OAuth providers that the administrator configures, and it needs SMTP settings for email. Shared workspaces, collections and environments work without the Enterprise license. A team of engineers who already sign in with a Google or Microsoft account and who accept manual onboarding and offboarding often fits this model. Review your own identity policy first, because a control that requires automatic deprovisioning on leaver events will not be met by manual accounts alone.
What does SAML-based SSO add in Enterprise Edition?
Enterprise Edition adds SAML-based single sign-on and OpenID Connect, so sign-in is handled by your existing identity provider rather than by local OAuth accounts configured on the Hoppscotch server. Centralizing authentication means that password policy, multi-factor enforcement and session rules come from one place. Your identity team should confirm which identity provider you use, which SAML attributes it sends, and how group claims map to Hoppscotch user groups before purchasing. Enterprise Edition also requires a license key, so plan for key management as part of the rollout.
Why does SCIM provisioning matter for API client users?
SCIM provisioning creates, updates and disables user and group records automatically from your identity provider. Without it, an administrator must remove a departing engineer from every workspace by hand, and an access review must compare lists manually. Hoppscotch Enterprise Edition lists SCIM user and group provisioning among its features. For a regulated team, ask who owns the deprovisioning process, how long a disabled account remains active in the workflow, and whether the SCIM mapping covers the groups that control workspace access.
Which audit and governance features need the Enterprise license?
Hoppscotch Enterprise Edition adds activity and audit logs and user groups, which give administrators a record of who changed what and a way to grant access by group rather than by individual. It also adds OpenTelemetry observability. Community Edition does not list these features, so if your evidence requirements call for an access history of shared API collections, verify the log content, retention and export options in the Enterprise documentation before you rely on them. Export the logs to your own SIEM if your audit plan requires central retention.
How much does Hoppscotch cost per user for the cloud product?
Hoppscotch's pricing page lists Hoppscotch Cloud Free at $0, Business at $6 per user per month and Enterprise at $11 per user per month, billed annually. These prices apply to the hosted cloud product, not to the self-hosted Enterprise Edition license, which is quoted separately. Use the cloud figures only as a reference point. Confirm current prices and the self-hosted license terms directly with Hoppscotch before budgeting, because pricing pages change and the self-hosted contract may include different terms.
Can a self-hosted Enterprise deployment be run by our own team?
Yes, if your team has the skills to operate the stack. Hoppscotch Community Edition is packaged as Docker containers, with separate frontend, backend and admin images or one all-in-one container, and the documentation includes a Helm chart guide for Kubernetes. The Enterprise Edition adds the license key and SSO configuration on top. Your team will need to handle backups of the PostgreSQL database, upgrades, TLS and monitoring. DeployOpen can plan, implement, integrate, harden, back up and document a self-hosted instance inside your own infrastructure under a written, fixed scope, and it offers ongoing support and upgrades as retainers. Ask for the scope in writing before work starts, and confirm which parts your staff will own afterward.
What drives the cost of each option
Postman's cost is mostly per-seat and add-on driven, while a self-hosted Hoppscotch Community Edition moves the spend onto infrastructure, database operations and staff time. Each card below names one cost component, whether it is one-time or recurring, and what to request in a written quote.
Postman seats and plan tier
Postman bills by plan and seat, and the Free plan since March 2026 is limited to one user who cannot create a team. A team that needs shared collections will pay for Team or Enterprise seats every year, so seat count is the main recurring line. Ask the vendor which plan each user needs, whether guest or viewer seats are priced differently, and how mid-term additions are prorated.
SSO and security add-ons
SSO on Postman is sold as an add-on on top of seats, and advanced administration sits in the Enterprise tier. For Hoppscotch, SAML SSO and SCIM belong to the Enterprise Edition, which requires a license key. Confirm in writing which identity features are included per seat, which are add-ons, and whether AI credit overages are billed on top.
Server and database hosting
Hoppscotch Community Edition is free to license but runs on your compute, with a PostgreSQL database set through DATABASE_URL. The documented prerequisites list 4 CPU cores and 4 GB of RAM for the build image and as little as 1 CPU core and 2 GB of RAM to host the output. This is a recurring infrastructure charge that depends on your cloud or data center rates, and it should be sized with your own team.
Backups, upgrades and SMTP
Community Edition is installed, administered and updated by you, with quarterly releases. Recurring work includes database backups and restore tests, applying upgrades, and maintaining the SMTP service that email sign-in depends on. Ask your team or a partner to estimate these hours in a fixed-scope plan, and budget them as ongoing operations rather than a one-off project.
Staff time and support
Community Edition support comes through the community forum, while Enterprise includes priority support and guaranteed quarterly updates. Internal staff time for administration, OAuth provider setup and user onboarding recurs as people change roles. For Bruno, the cost shifts toward Git hygiene and paid Pro or Ultimate seats if you need features such as full Git UI operations. Ask each vendor what response times and update guarantees are covered at your tier.
One-time migration and optional licensing
Moving collections has one-time costs: exporting from Postman, importing into Hoppscotch within the 50 MB self-hosted limit, rewriting scripts, and configuring team workspaces and OAuth. Enterprise licensing is optional and recurs per user per month on Hoppscotch's pricing page, billed annually. Request a written scope that separates one-time migration work from recurring licenses, seats and support, so the two can be compared on the same basis.
What a move from Postman to Hoppscotch involves
The sequence moves collections, environments and team access from Postman's cloud into a Hoppscotch Community Edition instance on infrastructure you control, with credentials kept out of version control. The result is a tested self-hosted workspace that your team can sign into and use for daily requests and CI runs.
Export collections and environments from Postman
Someone with access to the Postman workspaces exports each collection and environment as JSON, starting with the collections the team uses most. Bulk account-wide exports are available only to team admins, so confirm early who can request them and how long the download remains available. Store the exports in a restricted location, since environments often hold live tokens. You know this step is done when every collection your team relies on has an export file and each environment has been listed with its variable names.
Deploy and harden the Community Edition instance
Your platform or infrastructure team deploys Hoppscotch Community Edition using the Docker images or the Helm chart guide for Kubernetes, and connects it to a PostgreSQL database set through DATABASE_URL. Check the prerequisites first, since the build step needs more CPU and memory than hosting the output. Restrict network access, place the instance behind your standard TLS and identity controls, and set up backups for the database. You know this step is done when the instance starts, the database is reachable and a test account can load the workspace.
Configure OAuth sign-in and SMTP
The administrator enables the sign-in providers your organization allows, such as Email, GitHub, Google or Microsoft, and enters the client credentials each provider issues. Email sign-in and invitations need working SMTP settings, so test delivery with a real mailbox before inviting users. Confirm with your identity team whether the provider choice meets your access policy, and remember that SAML and SCIM are not part of Community Edition. You know this step is done when an invited user can sign in through the chosen provider and receive the invitation email.
Import collections within the self-hosted size limit
Import each Postman collection and environment through the Hoppscotch importer. Self-hosted editions accept files up to 50 MB, so split very large collections by folder before importing. Compare request counts, folder structure and environment variables with the Postman original, since imports can differ in how they handle scripts and auth settings. You know this step is done when each imported collection shows the same requests and folders as the source, and a sample request returns the expected response from a test endpoint.
Recreate team workspaces and access
Create the team workspaces in the self-hosted instance, then assign collections and environments to them according to how your team currently shares work in Postman. Map each Postman role to the access level that Hoppscotch offers, and review it with the owners of the APIs. Because the Community Edition handles provisioning by hand, record who has access and when it was granted. You know this step is done when each team member can open the workspaces they need and no one can see workspaces outside their role.
Move embedded credentials into environments
Find every API key, bearer token, password and client secret stored directly in requests, scripts or collection-level auth. Move each one into a Hoppscotch environment variable on the self-hosted instance, and replace the literal value with a reference to that variable. Do not commit these values to Git or to shared exports, and rotate any credential that was previously shared in plain text. You know this step is done when a search of the imported collections finds no literal secrets and every authenticated request runs from an environment.
Rewrite scripts and replace Postman CI steps
Review each pre-request and test script that the import carried over, rewrite the Postman-specific calls into Hoppscotch script equivalents, and run each request to confirm the assertions still pass. Then replace the Newman or Postman CLI steps in your pipelines with the Hoppscotch CLI, which is alpha and installed from npm as @hoppscotch/cli, and requires Node.js 22 or later. Confirm that the reports your pipeline needs, such as JUnit XML, are produced before you remove the old job. You know this step is done when the scripted tests pass against the self-hosted instance and the pipeline completes with the new command.
What do buyers ask before moving from Postman?
What does a move from Postman to a self-hosted Hoppscotch instance cost?
The cost comes from four components: the server and PostgreSQL database you run, the staff time to install, configure and upgrade it, the migration of collections and environments, and the Postman seats you still pay for during the overlap. Hoppscotch Community Edition is free to use under the MIT License, so the software line is zero, but the infrastructure and labor are not. Most of the one-time cost is migration and configuration, while server hosting, backups, upgrades and support recur. Ask any implementation partner for a quote that lists these components separately, tied to a written scope.
What drives the cost of moving API collections up or down?
The main drivers are the number of collections, how many of them use Postman scripts that must be rewritten, how many environments hold secrets, and how many people need shared team workspaces. Collections built on OpenAPI or on clean Postman v2.1 exports move faster than heavily scripted ones. Sign-in design matters too: setting up OAuth providers such as GitHub, Google or Microsoft, plus SMTP for email, adds configuration work. A smaller, well-documented collection set with few scripts usually keeps the engagement small.
How long does a migration from Postman take?
The timeline depends on scope, not on a fixed duration. The steps are inventory of workspaces and collections, export, import, script rewriting, environment and secret handling, server installation and sign-in setup, and a parallel run before cutover. The Hoppscotch importer accepts Postman collections and environments, but the 50 MB limit on self-hosted editions and the number of scripts to rewrite can extend the work. Ask for a written timeline that names each milestone and what the client must review before the next one starts.
What must our team provide before the work starts?
Your team needs to supply a list of workspaces and their owners, a sample export of collections and environments, the hosting target with its container runtime and PostgreSQL access, DNS and TLS decisions, SMTP settings, and the identity provider details for OAuth sign-in. Security and compliance staff should confirm where credentials and tokens may be stored and who approves access. Engineers should identify which API test runs depend on Postman or Newman in CI. Agree on these inputs in the written scope so that delays do not come from missing access.
Can our own engineers do the migration without outside help?
Yes, for a small team with few scripts and an engineer who can run containers and a PostgreSQL database. Hoppscotch Community Edition is installed and administered by the user, and the vendor documents the Docker and Helm deployment paths. The harder parts are rewriting Postman scripts, designing secret handling, and keeping the instance patched on the quarterly release cadence. Outside help is most useful when the migration must meet audit evidence requirements or when many collections depend on custom scripts. Confirm your internal capacity before choosing a path.
Do we need the Enterprise Edition to get SSO with SCIM?
Yes, if you need SAML-based SSO, OpenID Connect, SCIM user and group provisioning, or activity and audit logs. Hoppscotch Community Edition signs users in through Email, GitHub, Google and Microsoft OAuth providers configured by the administrator, which covers many teams without the paid tier. The Enterprise Edition requires a license key and adds SCIM, audit logs, user groups and priority support. Confirm the exact features and license terms on Hoppscotch's pricing and self-hosting pages before you decide.
Does moving to Hoppscotch keep our collections inside our own infrastructure?
Yes. A self-hosted Hoppscotch instance stores team workspaces in a PostgreSQL database that you run, so collections, environments and any embedded credentials stay on infrastructure you control. Postman's EU Data Residency instance in Frankfurt is sold only to Enterprise customers. Your data residency review should still confirm backup locations, log retention and where the client builds its image, because those choices sit with your team rather than with the software.
How DeployOpen helps teams evaluate and move
DeployOpen can take the Hoppscotch decision and the migration off your team's plate, but it starts with a written scope. DeployOpen is a Chainscore Labs company. It plans, implements, integrates, hardens, backs up and documents self-hosted open-source platforms inside your own cloud accounts, data centers or isolated networks. For a Postman exit, that can mean standing up a Hoppscotch Community Edition instance with its PostgreSQL database set through DATABASE_URL, configuring the Email, GitHub, Google or Microsoft sign-in providers you choose, setting up SMTP, and writing the backup and upgrade routine for the database and container images. Before any of that, an evaluation can confirm which of your collections, environments and scripts import cleanly and which need rewriting.
Most migrations are fixed-scope engagements. Scope, deliverables and timelines are agreed in writing before work starts, so the boundaries are clear: which teams and workspaces move, whether the Postman importer, OpenAPI import or manual rebuilds are used, how many collections are rewritten, whether the hopp test CLI runs in your pipeline with JUnit XML reports, and who signs off on each step. DeployOpen does not publish a price list. A quote follows from that written scope, so the inputs to ask for are the number of collections and environments, the import size of the largest export against the 50 MB self-hosted limit, the sign-in and SSO requirements, and the hosting target.
After go-live, teams often want someone to keep the instance patched, apply quarterly Community Edition releases, rehearse restores and re-run security testing. DeployOpen offers ongoing support and upgrades as retainers, which recur, while the migration itself is a one-time fixed-scope cost. Ask whether a Hoppscotch Enterprise Edition license key, with SAML SSO and SCIM, is in the quote or left as a separate purchase decision. Note that DeployOpen is not a Hoppscotch partner or reseller, and that it prepares evidence for compliance assessments without issuing audit reports or certifications. Ask for the written scope and confirm each assumption against your own environment before signing.
