# Introduction

> FacePing is face verification for your app that runs on the device, so it keeps working with no network. Pick your platform and see a match on your own phone in about 10 minutes, on a machine that already builds mobile apps.

Source: https://docs.faceping.ai/

FacePing checks that the person in front of the camera is the person you expect: someone with a ticket at an event, a member at the gym, a visitor at a kiosk. Every check runs **on the device**, with liveness built in: under 0.3 s per face check, and about 1.7 s for a live check with a head turn.

## Get going in 10 minutes

Pick your platform. You'll sign up for a free sandbox key, add one package, and verify your own face on your own phone. Then switch on airplane mode and verify again. The 10 minutes assume your machine already builds apps for your phone; each guide links to the set-up if it doesn't.

- [.NET MAUI](https://docs.faceping.ai/start/maui/): Available in preview
- [Flutter](https://docs.faceping.ai/start/flutter/): Available in preview
- [React Native](https://docs.faceping.ai/start/react-native/): Available in preview
- [iOS (Swift)](https://docs.faceping.ai/start/ios/): Available in preview
- [Android (Kotlin)](https://docs.faceping.ai/start/android/): Available in preview
- [Capacitor](https://docs.faceping.ai/start/capacitor/): Available in preview
- [Avalonia](https://docs.faceping.ai/start/avalonia/): Available in preview

No card and no approval for the sandbox. You apply once, when you're ready to go live.

## How it works

1. **Enrol.** A person opts in and takes a selfie. The photo is turned into a face template and discarded. In the sandbox you enrol on the device, or on one practice check-in list through the API, the widget or the dashboard's front desk; in production, people enrol with consent through your server, the [FacePing widget](https://docs.faceping.ai/widget/) or the dashboard.
2. **Sync.** Each device downloads an encrypted copy of just the faces it needs, for one check-in list. After that it works offline.
3. **Verify.** Your app asks "is this person `A1234`?" FacePing compares the live face against **that one enrolment only** (1:1), checks it's a real face and not a photo, and answers `Match` or `NoMatch`.
4. **Forget.** Faces are deleted when someone withdraws, when you remove them, when your list ends, or when a face reaches the maximum age you set for an ongoing list, on the server and on every device.

Enrolment and verification run in the FacePing core, one native engine written in Rust, the same on the phone and on our servers. See [Security](https://docs.faceping.ai/security/).

The ID is yours: a ticket number or membership number. FacePing never needs a name.

## What people build with it

| Use case | How it fits |
| --- | --- |
| **Events and ticketing** | A fast face lane at the entrance, checked against each ticket, offline. |
| **Gyms and memberships** | Members walk in without a card, and cards can't be shared. |
| **Clubs and venues** | Members and pass holders check in on a shared tablet on site, alongside a non-face way in. |
| **Kiosks and visitors** | Pre-registered visitors confirm who they are at reception or a self-service kiosk. |

Whatever you build, FacePing only does 1:1 verification by default, and people who don't opt in always get another way in. Need to identify someone from a crowd of enrolled faces (1:N)? Ask us when you apply.

## Next steps

- [How the SDK works](https://docs.faceping.ai/sdk/): Enrolment, verification, liveness, storage and the sandbox.
- [Going to production](https://docs.faceping.ai/going-live/): Apply, enrol real people with consent, and sync faces to devices.
- [Server API](https://docs.faceping.ai/quickstart/): Create check-in lists, enrol people and manage deletion from your server.
