Backup & Recovery
Define the records to capture and the recovery you need to prove.
- Object and file scope
- Capture schedules and snapshot storage
- Restore previews and validation
For developers and platform teams
Build around your data.
Keep control of the connection.
Start with a product, a source system, and the environment you operate. Find the guide for your setup, then work through the data flow and access model with your team.
Choose your starting point.
Data Archiving
Move historical data into your database and keep it useful.
- Source selection and relationships
- Archive runs and historical retrieval
- Verification and lifecycle controls
AI Connectivity
Give an agent a defined, inspectable path to enterprise data.
- Source identity and permitted fields
- MCP tools and bounded queries
- Source links and execution evidence
Working with ServiceNow, Linux, Docker, or a different database? Browse every configuration.
Make the data path explicit.
A good integration starts with a clear contract: what it can read, what it can change, where the result goes, and how you verify it.
Live access and stored history
Live queries use the configured source identity. Stored snapshots and archives need their own access and retention controls. Define both boundaries when designing your workflow.
- 1
Choose the source
Salesforce or ServiceNow. Name the objects, tables, fields, and related records your workflow needs.
- 2
Set the boundary
Define the source identity, permitted operations, deployment, and data destination.
- 3
Connect the workflow
Configure the product around the archive policy, backup job, or agent query you want to run.
- 4
Verify the result
Check returned records, denied access, interrupted work, and the evidence required for acceptance.
Bring these questions to implementation.
Identity and permissions
Which user or service identity connects to the source? Which objects, fields, and operations should be allowed? How will revoked access be tested?
Infrastructure and recovery
Who operates the host and database? Where do credentials and state live? How will the team recover after an interruption?
Data completeness
Which related records and files belong in scope? How will you recognise incomplete captures, missing references, or truncated query results?
Operational acceptance
What should happen on expiry, rate limits, validation errors, or a failed write? Which logs and result checks will the operator review?