Create the account
Sign in to the Project X IT client portal as the customer owner or an authorized tenant administrator.
On-premise deployment option
Resilience Workbench inside your environment.
Keep business, identity, asset, audit, vendor, and risk evidence under your organization's control. The customer-hosted edition uses customer-controlled PostgreSQL storage, server-validated licensing, hardened deployment guidance, and release software-bill-of-materials evidence.
Data boundary
The customer keeps the sensitive records.
Local evidenceDirectory imports, financial context, scanner results, collector output, system security plan data, risk scenarios, and reports remain in the customer-operated environment.
License serviceThe Project X IT account portal authenticates the customer and delivers a signed license file. The license controls employee volume, modules, validity dates, and revocation metadata without receiving customer evidence.
No card dataPayment information is collected by PayPal, Square, Stripe, Authorize.Net, wallet, ACH, wire, or another hosted provider. The portal stores provider references only.
Release evidenceAuthorized releases are accompanied by integrity hashes, pinned image identifiers, and machine-processable SPDX or CycloneDX software bills of materials for customer verification.
How trial licensing works
A customer can start without waiting on a manual key.
The license request is enforced server-side, and automatic issuance requires a billing reference first.
Complete hosted checkout
Select an enabled provider in Billing and complete checkout on the provider's site. Project X IT does not collect card or bank-account fields.
Request the license
After the provider confirms the transaction server-side, request the signed 30-day trial license and approved employee volume.
Receive the release
Authorized customers receive the versioned package or container entitlement, integrity manifest, SBOM, license file, and release notes.
Deploy and validate
Use the container path or customer-managed PostgreSQL path, mount the license as a read-only secret, and complete the acceptance checklist before importing evidence.
Operate and renew
Customer administrators monitor capacity, backups, security logs, certificate validity, and license status from their own environment and account portal.
Deployment choices
Choose the operating model that fits your environment.
The customer guide covers release verification, container and customer-managed database paths, licensing, hardening, backup, restore, and ongoing security operations.
Container deployment
Run the Workbench, PostgreSQL, and reverse proxy with Docker Compose for evaluation and approved smaller deployments.
External PostgreSQL
Use customer-managed PostgreSQL when the database team needs direct ownership of storage, backup, monitoring, and encryption controls.
License activation
Complete provider-hosted checkout, obtain the signed license, mount it as a secret, and monitor licensed employee volume without sending evidence to the account portal.
Release verification
Verify package hashes, image identifiers, release notes, and SBOM artifacts before approving the software for customer data.
Security operations
Set customer-owned TLS, logging, MFA, secrets, audit review, and incident response practices before production use.
Authorized release access
Versioned packages, registry access, source access when contracted, licenses, SBOMs, and integrity manifests are provisioned to authorized customers through onboarding.