Environments

Overview

ID Dataweb provides two fully segregated environments: preproduction and production. Each has its own Admin Console and its own API platform. The environments share no infrastructure — data, workflows, and credentials in one environment have no relationship to the other.

	Preproduction	Production
Admin Console	preprod.admin.iddataweb.com	admin.iddataweb.com
API base URL	`https://preprod1.iddataweb.com`	`https://prod2.iddataweb.com`
Use for	Development, testing, evaluations, POCs	Live production traffic
Infrastructure	Lighter-weight, shared resources	Full cloud resources, high availability
Monitoring & alerting	Basic	Full monitoring, alerting, and on-call coverage
SLA	None	Production SLA applies

Preproduction

Preproduction is where you build, configure, and test. Use it for:

Initial workflow setup and configuration
Integration development and testing
Evaluations and proof-of-concept work
Testing workflow changes before promoting to production

Preproduction runs on lighter-weight infrastructure with no high-availability guarantees and no production SLA. It is not intended for live user traffic. Occasional downtime or degraded performance should be expected during maintenance windows.

API keys, credentials, and test data in preproduction are isolated from production. Transactions run against test data sources — results do not reflect real-world identity decisions.

Production

Production is the live environment for real verification traffic. Use it once your workflow is configured, tested, and ready for end users.

The production environment runs on full cloud infrastructure with high availability, auto-scaling, and complete monitoring and alerting coverage. All production API traffic is actively monitored with on-call support. The production SLA applies to this environment.

API keys must be obtained separately for production — preproduction keys do not work against the production API. Contact your ID Dataweb team to provision production access.

Moving Workflows Between Environments

Workflows cannot be synced automatically between environments, but they can be exported and imported as JSON files via the Admin Console.

To promote a workflow from preproduction to production:

In the preproduction Admin Console, open the workflow you want to promote.
Export it as a JSON file using the export option in the workflow menu.
In the production Admin Console, navigate to the Workflows section.
Import the JSON file to create the equivalent workflow in production.
Obtain new API keys for the production workflow — keys are environment-specific and are not carried over in the export.

Related Resources

→ Org Structure | → User Management & Permissions | → SSO