Hosting and infrastructure

Apiable hosts the control plane 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 the parts Apiable runs. For specifics such as the region of your deployment and service-level terms, contact Apiable.

Where does Apiable run?

Apiable hosts the dashboard control plane and your branded API Portal on AWS. Your API traffic runs on your own gateway. Apiable configures the gateway and serves the portal, but live API requests go to your gateway and backend, not to Apiable.

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 an 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 using DNS validation. When you add a custom domain, Apiable requests the certificates and generates CNAME records for you to add at your DNS provider. It waits for the certificate to be issued before switching your portal to the custom domain.

Certificate provisioning runs in AWS Certificate Manager, with certificate requests 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 is a distinct tenant with its own configuration. A portal has its own custom domain, its own certificates, and its own access settings, and is identified by its subdomain. Portal-level settings apply only to that portal.

Settings such as restricted portal access and MFA are configured per portal and enforced at that portal's edge. The portal's configuration, including its custom domain CNAME records and certificate references, is held per tenant. See Portal security and MFA.

What should I confirm with Apiable for my deployment?

Confirm the AWS region for your portal and data, and the service-level terms that apply to you. This page describes the hosting model from the shipped product. Region placement for a specific portal, data-residency commitments, and availability terms are set per customer.

Where to next