Before you
connect.

Airgap is a pre-launch backup product for businesses using AI agents. Its approach is to keep an independent recovery copy outside the permissions granted to those agents, with recorded action information and control over which saved items to restore. Google Workspace is built; the service is not live yet.

Professionals and businesses using connected agents to do useful work, and agencies doing that work for clients. Airgap is not live yet. Join the homepage waitlist for launch updates and tell us which integrations matter to you.

Airgap is not live yet. Google Workspace is built. The homepage waitlist lets you share preferences for Google Workspace and possible future integrations. A preference is not a connection, active backup or promise of support. Check the integration page for the intended Google Workspace scope and account requirements.

Yes. Google provides native recovery capabilities for Drive and Gmail, with defined conditions and time limits. An independent backup is a separate question: what copy remains available, who can delete it and how will you restore the work you need? Google's recovery documentation

Yes. Notion describes provider backups and offers workspace exports. Those exports have scope limitations, and uploading an export does not instantly recreate the original workspace. Independent backup should be evaluated against the recovery you actually need. Airgap's Notion integration is planned for launch. Notion's export documentation

Airtable offers automatic and manual base snapshots, with plan-dependent retention and restore requirements. Those capabilities are useful; they are not the same question as whether a separate recovery copy sits outside your agent's permissions. Airgap's Airtable integration is planned for launch. Airtable's snapshot documentation

Airgap is pre-launch and is not available to buy or connect through the waitlist. You can join on the homepage and select the integrations you want. Joining does not create an active backup or grant any app permissions.

It can if the effective permissions it holds allow both operations. The relevant distinction is authority: keeping a copy in another folder does not by itself prove that the agent cannot reach or remove it.

It means the permissions already granted to your working agents are not also the authority to access or destroy the independent recovery copy. That is the intended separation in Airgap's design. It is not a claim that no administrator or system component has any access.

The distinction here is separation of authority from the permissions granted to your agents. It does not mean that a SaaS backup is stored on physically disconnected media. See the recovery approach for the intended boundary and its limits.

No. Backup provides a possible path to recovery after captured data is changed or deleted. Careful permissions, approvals and other execution controls still matter. A backup cannot reverse every email sent, transaction made or external action taken.

Attribution depends on the information available from the source. When a recorded actor is known, the history can show it. When it is unavailable, the record should say unknown rather than infer an identity.

The intended recovery experience lets you choose supported saved items and versions instead of assuming everything must be rolled back together. Check the integration’s supported objects, destinations and limitations.

Not from an Airgap copy that does not exist. Recovery depends on a successful capture made before the relevant loss and a saved version that is still available. Native provider recovery may offer other options depending on the incident.

Recovery time depends on the source, the amount and type of data, the selected recovery and the destination. Use a measured example relevant to your workload rather than assuming an instant restore.

Review the intended destination before confirming a recovery. Behavior varies by integration: do not assume every source restores in place, creates a new copy or supports merging.

After the relevant data has been captured successfully. Payment and account connection are setup milestones, not proof of a completed backup. Check the captured scope, completion result and freshness; a partial capture needs attention to the missing items.

Yes. A suitable rehearsal helps establish what can be restored, which permissions are required and where the recovered work appears. Use appropriate test items and a destination that will not disrupt live work.

The intended journey has three clear stages: connect an account, review supported data and check the first backup. Account selection, provider consent or administrator approval can add interactions. Airgap is pre-launch; joining the waitlist does not begin setup. Three stages does not mean exactly three clicks.

Airgap is pre-launch. The built Google Workspace capture path requires administrator approval for your customer’s Workspace account through domain-wide delegation. Capture is limited to the single account using your purchase email. New purchases for personal Gmail accounts are currently unavailable. You do not need administrator access or app permissions to join the waitlist.

Free guided implementation is offered for the first 200 integrations. The monthly subscription is separate; implementation scope and availability are confirmed with the team. You can prepare a planning brief locally. Booking and submission are currently unavailable.

Airgap is pre-launch and checkout is currently unavailable. Join the homepage waitlist for launch updates; no call or payment is needed to join. Already-paid customers can sign in with their purchase email to resume the existing setup journey.

The systems its agents use, the client work that matters, current permissions, recovery ownership and implementation needs. Prepare an outline of the workflow; do not put credentials or client data in the planning brief. The current booking page saves a local draft only; it does not reserve an appointment.

Evaluate it against the data sources, retention, independence and recovery behavior you need. Existing provider recovery or other backup tools may still serve a useful purpose. Choose based on supported coverage and a credible recovery path, not a blanket replacement claim.