# Bird vs Gigs for embedded connectivity Bird brings mobile connectivity and customer communication into one platform. Gigs offers a dedicated telecom stack with hosted checkout, subscription billing and operations tools. Choose the model that fits your product, customers and operating team. [Talk to an eSIM specialist](/demo?product=esim-migrate-gigs) [Create an account for eSIM](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fesim) [Explore the eSIM platform](/products/esim) ## Which service model fits your business? Compare how each platform connects the offer, purchase and first use. Then match coverage, service terms and integration options to your business. | Capability | Bird | Gigs | Who wins | | --- | --- | --- | --- | | Offer selection | Coverage, allowance, validity and price come together in the customer offer. | Project plans declare allowances, coverage, requirements and price. | Even | | Additional data | Top-up offers match the customer’s existing eSIM, with a clear additional purchase. | Eligible add-ons attach additional allowance to a subscription. | Even | | Installation | Private QR codes and supported same-phone setup guide the first connection. | Gigs Connect provides device setup guidance, QR codes and installation links. | Even | ## A focused operating system for connectivity. Gigs provides a dedicated telecom stack: Connect for checkout and subscriber management, Payments for billing, and an API for plans, subscriptions, SIMs and porting. Teams adopting that stack can use its hosted customer journey. ### Hosted customer journeys Gigs Connect covers checkout and continuing subscription management. Review branding, payment handling and the supported self-service changes against your requirements. ### An API integration Gigs documents plans, subscriptions, SIMs and porting as distinct resources. Use those contracts to estimate the integration and operational work. ### Employee phone plans Gigs for Work combines employee line administration with provisioning and integration options. Compare the actual countries, plans and support arrangement for your team. ## Put connectivity beside the customer relationship. Choose Bird when connectivity belongs inside the customer and business workflows you already run with Bird. Bring the offer, installation and ongoing service into a product journey, then connect the useful customer communication and operational follow-up. ### Travel and mobile journeys Build travel data and recurring mobile plans around your customer. Bring data, calls, SMS, number portability and ongoing service into the experience you offer. ### An embedded experience Connect the purchase, installation and ongoing service to your customer account. Keep useful messages and support close to the plan, through the channels your customers already use. ### A team that can operate it Use order, profile and package references to investigate a purchase. Include the source and freshness of observations in your evaluation, and agree the support responsibilities for the proposed service. ## Test one happy path and one recovery path. Select the same destination, device and service requirements. Complete an approved purchase, install the profile and verify the included data, calls or messages. Then test an interrupted setup or a declined port and compare the information available to the customer and support team. ### Compare the exact offer Review the exact allowance, speed policy, coverage, roaming, validity and renewal terms. A larger headline country count does not establish a better offer for your customer. ### Follow the financial result Inspect the published amount and currency, settlement arrangement, refunds and recurring obligations. Include ongoing support and integration responsibilities in the decision. ### Read the observations accurately Purchase, installation, network attachment and usage are separate signals. Both an unknown state and a delayed usage report need an understandable customer experience. ## Move the service without losing the customer. Map customer identities, plans, profiles, active subscriptions, payment arrangements and support history before moving traffic. A provider change does not automatically transfer an installed eSIM or a payment authorization. Agree the supported migration path, including any new installation or number port, before inviting customers to switch. ## Questions about Bird and Gigs ### Can I move an installed eSIM by changing an API key? Do not assume an installed profile is portable between platforms. Confirm the supported service and profile migration path; customers may need a new installation or a number port. ### Is travel data the same as a mobile subscription? No. A travel package commonly provides a bounded data allowance. A mobile subscription can include a continuing billing relationship and supported voice, SMS and number services. ### Which provider is cheaper? Compare published offers for the same service and market, plus the agreed platform, payment and support terms. A universal cheaper-provider claim would hide material differences. ### Does a usage dashboard provide an immediate spending cap? Not by itself. Network reports can be delayed. Review any separate enforcement capability and its guarantee before presenting an allowance display as a live cap. ## Continue your evaluation - [Plan a migration from Gigs](/docs/guides/esim/migrate/gigs): Inventory the existing service and rehearse a controlled transition. - [Embedded connectivity](/products/esim/embedded-connectivity): Put plan selection, checkout and subscriber self-service inside your app. - [Mobile plans](/products/esim/mobile-plans): Offer recurring data, calls and SMS with renewals and number portability. - [Plans and pricing](/products/esim/pricing): Review the commercial components of your offering. ## Read the product documentation - [Gigs Connect](https://gigs.com/connect): Hosted checkout and subscription management. - [Gigs API](https://gigs.com/api): Integration model and service lifecycle. - [Gigs for Work](https://gigs.com/products/gigs-for-work): Employee phone-plan management. - [Gigs porting guide](https://developers.gigs.com/docs/porting/how-porting-in-works): Eligibility, requirements and request outcomes. - [Gigs usage reference](https://developers.gigs.com/api/latest/core/usage): Usage records and carrier reporting delays. - [Bird eSIM integration guide](/docs/guides/esim/api): Prepare your integration and operational journeys. - [Explore connectivity comparisons](/products/esim/compare): Start with the customer journey and operating responsibilities. ## Plan the transition before moving a line. Map existing subscriptions, profiles and billing arrangements to the receiving service. Confirm installation and number portability before asking customers to change. [Discuss a Gigs migration](/demo?product=esim-migrate-gigs) [Read the Gigs migration guide](/docs/guides/esim/migrate/gigs) ## Related resources - [eSIM connectivity guide](/docs/guides/esim/overview) (docs) - [What is an eSIM?](/explained/esim/what-is-an-esim) (answer) [Get an implementation brief](/learn/workspace?topic=esim)