Security & Backup

Keepit

Monitor your Keepit SaaS backups from Dex - connector health, backup summaries, latest history, and job information across accounts.

Dex connects to the Keepit Partner API so admins can check SaaS backup posture conversationally - list connectors (devices), read connector health and the reason behind an unhealthy state, pull account-wide and per-connector backup summaries, see the latest completed backup timestamp, and review or filter job information. On the MSP master connection Dex can list subaccounts and create a new subaccount behind approval. Keepit is an MSP global app: one shared API token covers the Partner hierarchy, and each Dex tenant is confined to its Keepit Account GUID (account_id), with the account path segment forced on every call. Admin-only - there is no end-user self-service, since the API cannot cryptographically bind a Dex user to a Keepit identity.

Start free →

What Dex does with Keepit

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

List Keepit connectors (devices) for this account
Read connector health status - and the reason when a connector is unhealthy or critical
Pull account-wide backup summaries covering every connector in one call, or per-connector summaries
See the latest completed backup timestamp for a connector
Review job information for a connector, or filter jobs by time range, active-only, or type (backup/restore/srestore)
List subaccounts under the Partner parent on the MSP master connection
Create a new subaccount under the MSP parent - with approval, master connection only
Deploy as an MSP global app - one shared API token, each tenant confined to its Keepit Account GUID via account_id

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>Is the backup healthy across this account, or is anything failing?
>Which connectors are unhealthy, and why?
>When did the last backup complete for the Exchange connector?
>Show me the account backup summary covering every connector
>List the failed backup jobs for this connector over the last week
>List the subaccounts under our Partner account

Policy actions

Every action Dex can take on Keepit is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`keepit_list_subaccounts`	List Keepit subaccounts under a parent Account GUID (MSP master connection only)	—
`keepit_list_devices`	List Keepit connectors (devices) for this account	—
`keepit_get_device_latest_history`	Read the latest completed backup timestamp for one connector	—
`keepit_get_connector_health`	Read health status and reason for one connector	—
`keepit_get_connector_backup_summary`	Read the backup summary for one connector	—
`keepit_get_account_backup_summary`	Read backup summaries for every connector in this account	—
`keepit_get_jobs`	Read job information for one connector	—
`keepit_filter_jobs`	Filter backup/restore job information for one connector by time range, active-only, or type	—
`keepit_create_subaccount`	Create a Keepit subaccount under the MSP parent (master connection only) - billing impacting	approval

How to configure Keepit

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In Keepit, create an API token (Users > Edit User > Security > Add API token) or via PMC, and store the token username and password shown once at creation.
2
Note your Keepit data-center hostname (e.g. dk-co.keepit.com or us-dc.keepit.com).
3
In Dex, enable the Keepit integration and paste the token username, token password, and api_host.
4
For the MSP master connection, leave account_id blank; Dex can then list subaccounts and map each tenant to its Keepit Account GUID.
5
On each tenant connection, set account_id to that tenant's Account GUID. Dex validates the token with a live read before saving.

Credentials required

token_username: Keepit API token username (secret; shown once at creation)
token_password: Keepit API token password (secret; shown once at creation)
api_host: Keepit data-center hostname (e.g. dk-co.keepit.com, us-dc.keepit.com) - hostname only, not a full URL
account_id: This tenant's Keepit Account GUID (e.g. nq2v51-5mx23m-qb7sah) - leave blank on the MSP master connection, set on each tenant connection

Requirements

•A Keepit subscription with an API token (Basic auth username and password)
•The correct Keepit data-center hostname for your region
•One shared API token covers the Partner hierarchy; each Dex tenant is confined to its Account GUID via account_id (path-forced)
•Admin-only - no end-user self-service, since the API cannot bind a Dex user to a Keepit identity
•Start-backup and restore submission are not available through Dex - use the Keepit UI