Overview

Digital Trust Foundry operates as a multi-tenant platform where each organization gets their own isolated tenant environment. This guide explains how to obtain and access your tenant.

Instances and Tenants

What are Instances?

Instances are regional deployments of the Digital Trust Foundry platform. Each instance operates independently and serves tenants in specific geographic regions.

What are Tenants?

A tenant is your organization’s isolated environment within an instance.

When a tenant is configured for you, it will be deployed in an instance corresponding to your geographical location.

Each tenant has:

• Unique subdomain — your-tenant.digitaltrustfoundry.com
• Isolated data — Complete data separation from other tenants in the same instance
• Independent configuration — Custom settings, API keys, and user management
• Dedicated resources — Your own cryptographic identities and signing capabilities

Tenant Structure

Instance (e.g., US1)
└── Tenant (e.g., acme-corp)
    ├── Users
    ├── API Keys
    ├── Enterprise Identity (organizational AID, optionally vLEI-bound)
    └── Officer Identities (delegated signing authority)

Sandbox Tenant

Overview

Sandbox tenants are designed for development, testing, and evaluation purposes. They provide full platform functionality in a non-production environment.

Key Features

• Full API Access — All APIs available with test endpoints
• vLEI Testnet — Issue and verify vLEI credentials in a simulated GLEIF/QVI environment, without involving a real Qualified vLEI Issuer
• Test Data — Safe to use with test credentials and mock data
• No Production Impact — All operations are isolated from production systems
• Cost-Free — Typically available for evaluation and development

Accessing a Sandbox Tenant

1. Request Access — Contact Digital Trust Foundry support. Provide your organization details, a desired subdomain, and the first administrator’s username, full name, and email address.
2. Receive Invite — Foundry support provisions your tenant and creates the first administrator account. The administrator receives an invite email with a one-time link to set their password. If it doesn’t arrive within a few minutes, check your Spam folder.
3. First Login — Open the invite link, set a password, then sign in at https://your-tenant.digitaltrustfoundry.com using your username (not email) and the password you just set. The first administrator account defaults to Edge signing — after signing in you’ll be prompted to install and connect the Foundry Wallet browser extension, which becomes your sign-in method from then on (one-tap login; password sign-in is disabled once the wallet is connected).

Sandbox Limitations

• Test Environment Only — Not suitable for production workloads
• Data Retention — Test data may be periodically cleared
• Rate Limits — May have lower rate limits than production
• vLEI Testnet — Credentials are issued through a simulated GLEIF/QVI environment rather than a real Qualified vLEI Issuer

Production Tenant

Overview

Production tenants are for live, operational use with real business data and production-grade security.

Key Features

• GLEIF QVI Integration — Full integration with GLEIF Qualified vLEI Issuers
• SLA Guarantees — Service level agreements for uptime and performance
• Enhanced Security — Production-grade security controls and monitoring
• Data Persistence — Guaranteed data retention and backup

Obtaining a Production Tenant

1. Prerequisites — Complete sandbox evaluation, define production requirements, and review security and compliance requirements.
2. Tenant Provisioning — Submit a production tenant request, complete the onboarding process, and configure production settings.

Production Requirements

• Contract — Production tenant requires a service agreement
• Security Review — May require security assessment
• Compliance — Must meet platform compliance requirements
• Support Plan — Production support plan selection

Next Steps

After obtaining your tenant:

1. Set up enterprise identity — See the Enterprise Identity section
2. Add team members — Configure users and permissions in User Management
3. Generate API keys — Create keys for application integration in API Keys & Monitoring
4. Start building — See the Quick Start Guide for a walkthrough