Get started
Build your implementation plan
Answer a short set of questions about your cloud, gateway and authorization setup. Get a plan with the work it takes, an owner for each piece and a target date, ready to send to your teams.
Connecting Apiable is a project for several teams: the people who run your API gateway, the people who run your authorization server, and whoever signs off security. This planner turns your answers into one plan that says what each team owns and by when. A question you cannot answer yet is not a blocker. Assign it to the person who knows, or come back to it later.
What is an implementation plan?
A written plan for connecting Apiable to your stack. It lists the work your answers require, who owns each piece, a target date for each, and the reason behind each decision.
Who should fill in the implementation plan?
The person leading the integration, usually a platform or tech lead. Questions that belong to a specialist, such as what your authorization server can put in a token, can be assigned to that person by name.
Do I need an Apiable account to build a plan?
No. The planner runs on this page and needs no account, so you can plan before you sign.
What happens to my answers?
They are saved in this browser on this device, and the planner doesn't send them anywhere. Download the plan as Markdown to share it, and use Start over to clear it.
What if our APIs do not run on AWS?
You still get a plan for the decisions that do not depend on your cloud: identity, authorization, owners and dates. The gateway connection itself follows the guide for your gateway. See API Gateways for Kong, Azure API Management and Apigee.
Can I change an answer later?
Yes. Change any answer and the plan updates. Work you no longer need is marked no longer needed rather than deleted, and the owners, dates and progress you entered are kept.