APIGit vs Stoplight
Stoplight is a visual API designer that works on top of a Git repository you host on GitHub, GitLab, Bitbucket or Azure DevOps, or keeps a project in its own storage. APIGit is the Git host: the repository, the pull requests, the published docs and the mock servers are in one place.
Stoplight is an API design and documentation platform by SmartBear. Facts checked against its public documentation on 19 November 2026.
APIGit
Stoplight
The short version
The repository is in APIGit
A Stoplight Git project reads and writes a repository on another Git host; a Stoplight project without Git keeps its data in Stoplight. An APIGit project is a Git repository with its own HTTPS and SSH address.
Review without leaving
Stoplight offers discussions and a graphical diff; pull requests happen on your Git provider. In APIGit the pull request, the reviewers and the merge are next to the editor.
Stoplight's open-source roots
Spectral, the linter APIGit's governance runs on, and Prism, a widely used mock server, both come from Stoplight.
Git, side by side
An APIGit project is a Git repository from its first commit. This is what that means next to Stoplight, topic by topic.
| Topic | APIGit | Stoplight |
|---|---|---|
| Where your API files live | Yes:In a Git repository that APIGit hosts: specs, Markdown and mock scripts as files | Partly:Git projects keep files in a repository on your Git provider; Stoplight projects keep them in Stoplight |
| Clone and push with any Git client | Yes:HTTPS with a token, or SSH at git.apigit.com | No:Stoplight is not a Git host: you clone from your own Git provider |
| Branches and tags | Yes:Git branches and tags, created in the browser or pushed from your machine | Yes:Git branches in Git projects; multi-branch support starts on the Startup plan |
| Pull requests and review | Yes:Built in: reviewers, approvals, and merge, rebase or squash | Partly:Discussions and a graphical diff; pull requests happen on your Git provider |
| Commit history and diff | Yes:Every commit of every branch, with a unified or split diff | Partly:A comparison of changes in Studio; history is on your Git provider |
| Working with GitHub, GitLab and others | Yes:Optional: two-way sync with a remote repository, or push mirrors (Enterprise) | Yes:Push and pull with GitHub, GitLab, Bitbucket and Azure DevOps; self-hosted Git on Pro Team |
- Yes:Has it
- Partly:Has part of it; the cell says which
- No:Does not have it
Feature by feature
Design, documentation, mock servers, governance, testing, agents and plans. Where Stoplight has something APIGit lacks, the table says so.
| Topic | APIGit | Stoplight |
|---|---|---|
| API design | ||
| OpenAPI versions | Yes:OpenAPI 3.0 and 3.1, Swagger 2.0 | Yes:OpenAPI 2.0, 3.0 and 3.1 |
| Visual editor for OpenAPI | Yes:A form view beside the code view, with a diff before you commit | Yes:A visual form editor and a code editor, with JSON Schema models |
| AsyncAPI and GraphQL | Yes:Both: edit as code, preview and publish, in the same repository | Partly:JSON Schema models; AsyncAPI only as Spectral lint rules |
| Documentation | ||
| Hosted documentation | Yes:One site for OpenAPI, AsyncAPI, GraphQL and Markdown, published from a commit | Yes:Hosted docs with a try-it console and Markdown pages |
| Custom domain | Yes:On Team and Enterprise | Yes:From the Startup plan |
| Try it console | Yes:Try It Out for OpenAPI, on every plan | Yes:Try it in the hosted docs |
| Private documentation | Yes:Members only, named external viewers, or a password-protected link | Yes:Private or public docs; SAML single sign-on from Pro Team |
| Mock servers | ||
| Hosted mock server from a spec | Yes:From OpenAPI documents or a GraphQL schema, with request validation | Yes:Hosted Prism mocks: static from examples or dynamic generated data, with request validation |
| Mocks with your own code and state | Yes:Express.js scripts from the repository (Team and Enterprise) | No:No custom scripts are documented |
| Mock on your machine | Yes:apigit mock serve, from the working copy | Yes:Prism is open source and runs locally |
| Governance | ||
| Style rules for API descriptions | Yes:Spectral: two built-in rule sets, your own on Enterprise | Yes:Spectral style guides in the editor; shared style guides on higher plans |
| Breaking-change check | Yes:apigit breaking, between two Git refs, in a terminal or in CI | No:Not documented |
| API client and testing | ||
| API client for sending requests | Partly:Try It Out in the reference; no standalone client or saved collections | Partly:Try it in the docs |
| Test scenarios, runners and monitors | No:Not provided | No:No test runner or monitors are documented |
| CLI and AI agents | ||
| Command line | Yes:apigit: lint, score, diff, breaking, preview, mock and publish; the checks run offline with no account | Partly:@stoplight/cli publishes a directory to a project; Spectral and Prism have their own CLIs |
| MCP server | Yes:One for each published document, and one for your account | Not covered in this check |
| Plans | ||
| Free plan | Yes:1 user, 1 published document, 1 mock server | Yes:1 user, 1 project |
| First paid plan | Yes:Team: $24 a month, 3 seats included; $8 per further seat | Yes:Basic: $44 a month billed yearly, 3 users included; $11 per further user |
Checked on 19 November 2026 against each vendor's public documentation and pricing pages. APIGit's column follows our documentation and pricing. Products change: if a cell is out of date, tell us and we will correct it. Product names are trademarks of their owners.
Sources
Where Stoplight is the better choice
A comparison that only lists our strengths is an advertisement. These are the things it does that we do not, or does better.
A visual designer for everyone
Stoplight's form editor, with JSON Schema models and shared component libraries, was built so that people who do not write YAML can design an API.
Spectral and Prism
Both are open source and widely adopted. Prism's dynamic mode generates data from the schema, and it runs anywhere. APIGit's governance uses Spectral.
It works on the repository you have
If your specs must stay on GitHub, GitLab, Bitbucket or Azure DevOps, Stoplight edits them there on every plan. In APIGit, sync with an external repository needs the Enterprise plan.
Choose Stoplight when
- Your specs must stay on the Git host you already use
- You rely on Prism's generated mock data
- You design JSON Schema models shared between many APIs
Choose APIGit when
- You want the repository, review, docs and mocks in one product, with no second Git host
- Pull requests should show governance findings beside the diff
- Mock servers need your own code and state
- You document AsyncAPI and GraphQL beside OpenAPI, and want an MCP server for agents
Moving an API from Stoplight
Start from the repository
A Stoplight Git project is already a repository of OpenAPI and Markdown files on your Git provider. Export a Stoplight project that is not on Git as files first.
Migrate it into APIGit
Use the migration when you create the repository to copy it in, or commit the exported files to a new repository.
Reuse your Spectral rules
Your Spectral style guide becomes a custom rule profile on the Enterprise plan, and apigit lint uses a .spectral.yaml in the working directory on any plan.
$ git clone git@git.apigit.com:acme/orders-api.git$ cd orders-api$ cp ~/Downloads/openapi.yaml .$ apigit lint openapi.yaml$ git add openapi.yaml$ git commit -m "Import the orders API"$ git pushQuestions about APIGit and Stoplight
What is the main difference between APIGit and Stoplight?
Is Stoplight Git-native?
Is Stoplight being discontinued?
Can I keep my Spectral style guide in APIGit?
How do the mock servers compare?
Other comparisons
- APIGit vs Mintlify
A documentation platform for product and API docs
- APIGit vs Postman
An API client and testing platform
- APIGit vs SwaggerHub
An API design platform, now named Swagger Studio
- APIGit vs Apidog
An all-in-one API design, debugging, testing, mock and documentation platform
- APIGit vs Redocly
An API documentation platform, with the open-source Redoc and Redocly CLI
- APIGit vs ReadMe
A hosted developer hub for API documentation
- APIGit vs Insomnia
An open-source API client with a spec editor
- APIGit vs Bruno
An open-source, offline API client
- All products in one table
The comparison overview
Try it yourself
Worked examples from the learn hub, each with the output of the tools.
- Run a mock server from an OpenAPI file on your machine
One command starts a mock that answers every operation of an OpenAPI file with generated examples and refuses requests that do not match the description. What it returns, how it validates, and when to move it to a hosted mock.
- Bundle a multi-file OpenAPI description into one file
Splitting an OpenAPI description over files keeps it maintainable; many tools still want one file. apigit bundle resolves the external $refs into components and leaves internal ones as references. A four-file example, the output, and why to lint the bundle.
- oneOf vs anyOf in OpenAPI: the one payload that tells them apart
oneOf needs exactly one schema to match, anyOf at least one. The difference only shows on a payload that fits two schemas: oneOf refuses it, anyOf accepts it. The same request sent to both, with a mock server's answers.
- "invalid-ref ... does not exist" and "Can't resolve $ref": finding a broken reference
An OpenAPI $ref that points to nothing. How a linter and a bundler report it, how to read the path in the message, and the five usual causes: a typo, the wrong section, a moved file, a missing escape, a case difference.
Put one API in a repository and see
Create a free workspace, commit the OpenAPI file you already have, and open a pull request against it. It is Git from the first commit.
Free for individuals. No credit card.
$ npm install -g @apigit/cli$ apigit auth login$ apigit doc publish