Skip to content
Provider onboarding

Plan your setup before adding more devices.

Work with the provider team to choose a setup, connect a first node, and plan rollout. Confirm integration options and payment terms before starting.

  • Plan first. Share scale, control, and deployment needs before rollout.
  • Clear consent. Ownership and opt-out stay explicit.
  • Connected devices. Review connections and activity after installation.
Illustration of staged provider deployment. Program acceptance and deployment options require confirmation.

Provider onboarding

See what to prepare at each rollout stage.

Move from application and integration planning to a representative node test, controlled rollout, and connected devices.

  1. Stage 01

    Provider application

    Tell us about your devices and network so we can discuss a suitable setup.

    What to prepare

    devices or network capacity you control or are authorized to manage
    primary regions and expected scale
    device types, operating systems, and installation plans
    expected availability
    how end-user consent is handled when end users are involved
  2. Stage 02

    Integration plan

    Choose a supported setup with the provider team.

    What to prepare

    the supported client or integration agreed with the provider team
    how devices are registered and who manages them
    how credentials are handled
    monitoring and support needs
    how users can disable or remove participation
  3. Stage 03

    First-node test

    Test one representative node before wider rollout.

    What to prepare

    successful installation or integration
    the node is signed in and appears online
    provider can identify and disable the node through the agreed process
    no secret or end-user personal data is exposed in public support channels
  4. Stage 04

    Controlled rollout

    Expand after the first-node path is understood and can be operated safely.

    What to prepare

    deployment inventory and rollout plan
    consent/authorization records where applicable
    the person responsible for the deployment and the support contact
    rollback or removal procedure
  5. Stage 05

    Connected devices

    Review connected devices and recorded activity after rollout.

    What to prepare

    confirmation that the first node connected
    7-day active node count when available
    current quality and eligibility status
    usage and activity shown in your account or provider reports

Available today

Standard AntGain client

Start with one supported device using the download page before expanding.

Plan with AntGain

Provider-scale deployment

Deployment options are confirmed during provider onboarding and must match current supported capabilities.

Planned SDK

Embedded Node SDK

An embedded Node SDK is planned but is not yet available for general use.

See the provider journey from application to connected devices.

Move from application and integration planning to the first online node, controlled rollout, and ongoing participation.

Provider milestone

Provider inquiry submitted
A clear milestone in the provider onboarding journey.

Provider milestone

Technical onboarding started
A clear milestone in the provider onboarding journey.

Provider milestone

First provider node online
A clear milestone in the provider onboarding journey.

Provider milestone

Provider node stays active
A clear milestone in the provider onboarding journey.

Provider milestone

Provider devices with recorded activity
A clear milestone in the provider onboarding journey.

Safe scaling

Grow with clear ownership, consent, and privacy.

Larger deployments still need clear user consent, secure credential handling, and responsible data practices.

Best practice 01

Keep credentials out of public intake

Do not submit passwords, API keys, tokens, private keys or device credentials in provider forms.

Best practice 02

Keep end-user and network data private

Do not submit individual end-user identities, residential IP lists or browsing/traffic records in public onboarding channels.

Best practice 03

Require understandable consent and removal

Third-party or embedded participation requires explicit, understandable consent and a practical disable/removal path.

Best practice 04

Confirm terms with the provider team

Check your provider account or agreement for payment and account terms.

Provider next step

Tell us about your devices and setup. Keep passwords and keys private.

AntGain will confirm the available deployment path after you share your scale and integration needs. Acceptance and commercial terms are confirmed separately.