Integration Development

Build your own integrations with JupiterOne when no managed integration exists for your data source, or when you need to ingest data from a proprietary or on-prem system.

The high-level flow:

1. Author a Custom Definition — describe the integration in the JupiterOne app: name, type, category, and which ingestion path it uses.
2. Pick an ingestion path — choose how data flows into the instance:
   • Custom File Transfer — upload CSV files directly. No code, no runner.
   • Custom integration: Code + Sync API — write code that pushes data via the Sync API using the instance's API key.
3. Run, query, iterate — JupiterOne tracks each ingestion as a job on the instance. Data appears in your workspace alongside managed integrations.

Custom Definitions

The concept hub. What a definition is, how instances and jobs relate, and how to author one in the JupiterOne app.

Custom File Transfer (CFT)

Upload assets and relationships as CSV files. Use this when your data is already in tabular form.

Custom integration: Code + Sync API

Push data via the Sync API from your own runner. Includes guiding principles for entity modeling, naming, and schema design.