Question 1

Can we use our own SSO provider?

Accepted Answer

Yes. Enterprise includes SSO support, organization roles, member management, and audit logs so access can follow your internal identity and review process.

Question 2

Where are bundles and account data hosted?

Accepted Answer

For standard Capgo Cloud, Supabase processes the primary database, authentication, account data, app and bundle metadata, and device identifiers in London, United Kingdom. Google Cloud provides database read replicas and regional infrastructure in Hong Kong, Tokyo, Sydney, Johannesburg, Milan, Jeddah, Mumbai, Sao Paulo, and Columbus. Bundle storage and live-update delivery use Cloudflare’s global infrastructure, including the USA. Enterprise can use regional endpoint routing for the live-update path or a licensed self-hosted deployment when different control is required. The up-to-date sub-processor list contains the full provider, location, and transfer details.

Question 3

Where is the current sub-processor list?

Accepted Answer

Our public sub-processor list is the current source of truth. It is kept up to date and includes each provider’s purpose, processing location, transfer mechanism, and change history.

Question 4

Can updates be self-hosted or delivered from our infrastructure?

Accepted Answer

Yes. Enterprise supports hosted, dedicated, hybrid, and licensed self-hosted deployment options when control requirements are more important than a standard SaaS setup.

Question 5

What reliability commitment is available?

Accepted Answer

Enterprise includes a 99.9% monthly availability commitment for the production platform. If the commitment is missed, service credits range from 10% to 30% based on monthly availability. Initial support targets are P1: one hour, 24/7/365; P2: two business hours; P3: one business day; and P4: two business days. Global replication, signed delivery, and rollback workflows support production recovery.

Question 6

Does regional replication multiply storage or bandwidth?

Accepted Answer

No. Each bundle is counted once for storage, regardless of the delivery regions it serves. Capgo bandwidth counts user-device downloads that are not served from the edge cache. Cache-served deliveries do not count against your Capgo bandwidth usage.

Question 7

Should we use channels or separate app IDs for flavors?

Accepted Answer

Use channels when flavors or environments share the same native app ID. This keeps your release setup simpler and groups those channels under one Capgo app. Use separate app IDs when a flavor needs a distinct native bundle ID, signing identity, entitlement set, or store listing; a device is not deduplicated across those app IDs.

Question 8

Can we keep our existing CI and use Capgo only for native builds?

Accepted Answer

Yes. Keep private dependency setup, web builds, Capacitor sync, and custom preparation in your CI. Capgo Build receives the prepared native project to compile, sign, and optionally submit to the stores. Supported build configuration can be passed as environment variables.

Question 9

Can Capgo work with our MSA, DPA, NDA, or PO flow?

Accepted Answer

Yes. Enterprise conversations can include custom payment processes, purchase orders, signed non-disclosure agreements, DPAs, and procurement workflows before rollout.

Question 10

Can your team build or fix Capacitor plugins for us?

Accepted Answer

Yes. Enterprise can include priority plugin fixes, migration support, and custom plugin work when your release path depends on native functionality.

Question 11

What payment and procurement terms do you support?

Accepted Answer

We support Stripe payment options plus custom enterprise payment processes for finance teams that need invoices, purchase orders, or procurement-system workflows.

Question 12

Are Capgo plugins included with Enterprise?

Accepted Answer

Enterprise includes access to the Capgo plugin ecosystem, priority plugin support, and a path to replace proprietary enterprise plugin dependencies where needed.

Question 13

How do you migrate us from another live-update platform?

Accepted Answer

We plan the migration with your team, map channels and environments, test rollback behavior, and can run both systems side by side until the cutover is safe.