Build, maintain, and automatically update your API documentation in the cloud
Hosted on global CDN
These were all unproven myths…until now.
No operations docs-like-code is now a reality with Redocly Workflows.
Previews are like staging areas, except better – you have unlimited preview environments! This flexibility allows for more nimble workflows with as much safety as a single staging environment. Previews are built automatically upon the creation of any pull requests.
Preview pull requests or branches automatically. Watch for the green checkmark in your favorite source control software and click it to see the preview. Working on public docs? You can still password-protect your previews.
From correctness with the OAS3 schema to grammar and style checking or corporate governance, we’ve got you covered.
Your production or previews (or both) can be protected by access controls:
Enabling your API definitions as a single source of truth.
Glues your API definitions to other elements of your API lifecycle. Cascades previews and builds of other docs.
Docs-like-code means treating your documentation like you treat your source-code:
This allows the docs to share certain benefits that the version-control products have spent years improving. Deploying code is hard, and there are often entire job roles dedicated to that task. Redocly Workflows takes that job (as it relates to the docs) and we do it quite well.
Docs-like-code requires a chain of tools (sometimes complex) to be set up and orchestrated to help you from local development to deployment. The days of complex scripted deployment pipelines are numbered. Redocly has created a service called Workflows to automate the delivery pipeline.
Redocly can connect to private repositories. You can still choose to publish your docs to the public or keep them protected by access control.
Please see our pricing to understand more about our various plans. The number of organization owners and members (our terms for people you collaborate with on your team) who have access is limited based on the plan.
We have integrations with the common version-control software providers, such as GitHub. We subscribe to events so that we know when a change is made to an API definition. That triggers a build, where we gather, validate, build, and deploy (depending on the branch, to prod or a preview environment).
It depends. First, is there a real business case to keep workflows on-premise? Second, right now workflows depend on some AWS-specific services, so it is possible to run in your own AWS-account cloud, but not on your own premise. It is possible to build our reference docs and developer portal on-premise without using workflows. Workflows adds the glue between different projects.
Yes, as long as you are on the professional plan or higher. In order to use a custom domain, you must point your CNAME record to ssl.redoc.ly. You can see our help docs to learn more about how to set up a CNAME record and custom domain.
A preview is the modern equivalent of a staging environment. We name it a preview, because you may have unlimited preview environments (requires the pro plan or higher). Most infrastructure is designed for a single staging environment workflow. The environment is typically used for review or acceptance before deployment to production.
A preview is built automatically (depending on how you configure your settings) upon the creation of a pull request, for example. This flexibility allows for more nimble workflows with as much safety as a single staging environment.