Qualification
Is Apiable right for you?
A short, honest checklist before you book a call. Apiable is a great fit for some teams and a poor fit for others — we'd rather you find out here than three meetings in.
If you're already past this and want to see what Apiable does, the platform overview is the better page.
Five questions
The honest gating questions
If you can answer all five comfortably, the rest of this page just confirms the detail. If any one of them is a hard "no", we've flagged what that means below.
Do you already run an API gateway?
If yes, keep reading. Apiable is the portal layer on top of your existing gateway — we connect to it, we don't replace it. If you don't run a gateway today and don't want to introduce one, Apiable is not the right tool.
Are your APIs REST?
If yes, you're in scope. GraphQL-only programs are not supported today. If you have a mix of REST and GraphQL, talk to us — Apiable can sit in front of your REST surface even if other parts of your platform are GraphQL.
Do you need partners or developers to onboard themselves?
If yes, that's the problem we solve — self-service partner onboarding, plans, quotas, and (optionally) usage-based billing. If your audience is internal-only and small, you'll get less value from Apiable than from your gateway alone.
Do you need single-tenant deployment in your own cloud account?
Default delivery is managed SaaS in our AWS Frankfurt account. Single-tenant deployment into your own AWS account is available as a named item on your enablement package — talk to us early so we can scope it. We don't offer single-tenant in Azure or GCP today, and on-prem isn't available. If your concern is data residency rather than physical hosting, see the security page — Apiable does not proxy your API traffic.
Are you on AWS, or willing to host the portal in our infrastructure?
Apiable runs in AWS Frankfurt (eu-central-1). If you need US, APAC, or another EU region, talk to us — we've delivered multi-region rollouts and can scope yours.
Supported gateways
Which API gateways does Apiable support?
Honest about what's live, what's on the roadmap, and what isn't on the path today.
| Gateway | Status | Notes |
|---|---|---|
| AWS API Gateway | Supported | Primary gateway. Native Cognito pairing. Most-deployed pattern. |
| Kong | Supported | Konnect (cloud) and self-managed. |
| Apigee (X and Edge) | Supported | OpenAPI-based catalog sync. |
| Azure API Management | Supported | Direct integration with Azure API Management. |
| Other gateways (Tyk, Gravitee, Mulesoft Anypoint, etc.) | On request | Not on the current roadmap, but technically integrable. We'd build the connector for a committed customer — talk to us early. |
| GraphQL-only | Not supported | Apiable's product, plan, and quota model is REST-shaped today. |
| In-house / custom gateway | Case by case | If your gateway exposes OpenAPI specs and OAuth tokens, talk to us. |
| No gateway | Not a fit | Apiable is the portal layer on top of a gateway, not a replacement for one. |
For deeper integration detail on the supported gateways, see Apiable + AWS API Gateway and Apiable + Kong.
Deployment models
How is Apiable deployed?
Default delivery is managed SaaS in our AWS Frankfurt account — each customer gets a dedicated portal instance with its own database, no shared portal data with other customers. If you need the platform deployed into your own AWS account, that's available as a named item on your enablement package — talk to us early so we can scope it.
What we offer today
- ✓ Managed SaaS, single-tenant per customer (your own portal instance, your own database)
- ✓ Custom domain, branding, and CSS
- ✓ Hosted in AWS Frankfurt (eu-central-1) by default
- ✓ Multi-region rollouts on request for enterprise
- ✓ Single-tenant deployment into your own AWS account, as a named enablement-package item
What we don't offer today
- ✕ Single-tenant deployment in your own Azure or GCP account
- ✕ On-premises deployment
- ✕ Air-gapped deployments
- ✕ Self-managed on-prem licensing
For the security and data-flow implications of this, see the Security & Compliance page.
Where we'd say no
Probably not for you if…
- ✕ You need to run the portal inside your own non-AWS infrastructure (Azure, GCP, on-prem) and that's non-negotiable.
- ✕ Your APIs are GraphQL-only and you're not planning to expose REST.
- ✕ You don't operate an API gateway today and don't want to introduce one.
- ✕ You're on a non-roadmap gateway (Tyk, Gravitee, Mulesoft Anypoint, etc.) and need it working today — you can't wait for us to build the connector.
- ✕ You're a single-team internal API program with five callers — your gateway alone is enough.
Where we'd say yes
Probably a good fit if…
- ✓ You run AWS API Gateway, Kong, Apigee, or Azure API Management — and you want partners to onboard themselves.
- ✓ You're trying to monetise your APIs (usage tiers, plans, billing) and your gateway can't do that on its own.
- ✓ You've outgrown a homegrown developer portal and want to stop maintaining it.
- ✓ You need self-service partner onboarding so engineering isn't doing it manually anymore.
- ✓ You're on AWS and want a Cognito-native pattern.
- ✓ You have a deadline (launch, regulatory) and need to ship a portal in weeks, not quarters.
Still not sure?
If you've read this page and you're still on the fence, that probably means you have an edge case worth a 30-minute call. We'd rather spend the time confirming fit than skipping it. If we're not the right answer, we'll say so on the call.
See what your API program looks like as a revenue engine.
Join the companies monetizing API usage, scaling partner onboarding, and proving measurable business impact—without overloading their teams.