Hosting and infrastructure

Apiable hosts the dashboard and your API Portal on AWS. Your API gateway, your authorization server and your backend stay on your own infrastructure. This page describes that split and where the parts Apiable runs are hosted.

Where does Apiable run?

On AWS. The dashboard and API Portals run in the Frankfurt region, eu-central-1, by default. If you have the Platform API, its endpoint at your-portal.api.apiable.io runs in the Ireland region, eu-west-1. Confirm the regions for your deployment with Apiable.

Some deployments differ from the defaults, for example where a portal's sign-in runs in another AWS region. Ask Apiable for the regions of your portal, and for any data-residency commitment, before you rely on them.

This split is the no-proxy model: Apiable runs the management surfaces, and your APIs run where they already run. See The no-proxy model.

Does Apiable host my API gateway?

No. Your API gateway stays yours. Apiable connects to the gateway you already operate and configures it through the gateway's own management API. The gateway and your backend remain on your infrastructure.

For Amazon API Gateway, Apiable operates the gateway in your own AWS account through the AWS API Gateway client. It reads your APIs and provisions subscriptions, but it does not host or replace your gateway. See API Gateways for the gateways Apiable connects to.

How does Apiable provision SSL?

Through AWS Certificate Manager with DNS validation. When you add a custom domain, Apiable requests the certificates and gives you CNAME records to add at your DNS provider. It waits for the certificates to be issued before switching your portal to the custom domain.

Apiable requests certificates in AWS Certificate Manager in us-east-1 and eu-central-1. You manage the DNS records; Apiable manages the certificates. See Custom domain for the validation states and the full flow.

How are portals separated from each other?

Each portal has its own configuration, custom domain, certificates and settings. A setting you change for one portal, such as MFA, applies only to that portal.

The portal's configuration, including its custom domain CNAME records and certificate references, is held per portal. See Portal security and MFA for the settings you control per portal.

What should I confirm with Apiable for my deployment?

The regions your portal and its data run in, any data-residency commitment, and the service-level terms that apply to you. This page describes the default hosting model from the shipped infrastructure. Your agreement sets the rest.

Where to next