Procurement requires a fixed-cost license that can survive a multi-year program without surprise renewals or usage-based escalation.

Trekport licenses are seat-based and fixed-term. Pricing tiers are published before contract. No usage meters, no per-object surcharges, no telemetry-driven billing.

Critical systems run on Oracle estates that accumulated for two decades. The catalog includes constructs that no off-the-shelf converter handles cleanly.

The AST-based engine handles the long tail: compound triggers, package state, BULK COLLECT into record types, FORALL with SAVE EXCEPTIONS, %TYPE and %ROWTYPE references, and dependency-ordered grants. Out-of-scope artifacts are reported, not silently dropped.

Cloud sovereignty mandates exclude managed third-party services from the migration data path.

Trekport is a local install. There is no managed cloud component, no third-party processor in the data path, and no SaaS dependency. The engine talks only to your source and target databases.

Modernization programs span election cycles and personnel turnover. The migration artifact must be readable, reproducible, and operable by a team that did not perform the original conversion.

Conversion output is plain SQL on disk, organized in a deterministic catalog tree. Every transformation has a rule reference an auditor can map back to the engine source. Two runs from the same inputs produce byte-identical output. The next administration can reproduce the migration without access to the original conversion team.

FedRAMP, IRS Publication 1075, CJIS, and similar control frameworks require detailed inventory of every component that touches sensitive data.

Trekport's component inventory is small and documented: a Rust desktop binary, a Python conversion engine embedded via GraalPy, and standard PostgreSQL extensions (orafce, pgcrypto, pg_cron, pgsql-http). Every dependency is open source and SBOM-traceable. There is no closed-source cloud agent.