Answers before you commit.

We manage recurring testing and inspection workflows for testing contractors, keeping customer-defined requirements, scheduled work, evidence review, and prepared outputs connected. Connect asset context, governing rules, recurring obligations, field jobs, evidence, quality control, finished packets, retained records, and recurrence in one continuous operating record.

We built Stratum for testing contractors who run recurring regulated testing programs. UST petroleum testing contractors come first, and additional regulated testing industries follow as configuration packs ship.

Your team defines the requirements, review criteria, cadence, and output structure. We carry those decisions through every job, and they stay yours. We then keep the program connected to each customer, site, asset, scheduled job, evidence record, review decision, and prepared output as work moves.

We connect program definitions, customers, sites, assets, schedules, jobs, evidence, review decisions, and prepared outputs. The UST guide shows Stratum applied to one sourced industry workflow.

UST petroleum testing is live today, with every federal requirement in 40 CFR Part 280 transcribed against its source section. Fire suppression, backflow, elevator, and electrical testing follow as configuration packs on the same spine.

State requirements and the federal baseline run through the same configured workflow. Many states operate EPA-approved UST programs with requirements beyond federal 40 CFR 280, and your team configures the cadences, forms, and outputs your state requires.

Your team owns its configuration. We provide a starting configuration to copy from, the copy is yours to adapt, and platform updates never rewrite the configuration your program runs on.

No. Dispatch and crew-scheduling software moves technicians through a day of jobs. We manage the regulated testing program itself: the requirements that apply, the jobs they generate, the evidence each job must produce, the recorded review decision, and the prepared output.

We replace the spreadsheets, shared folders, paper forms, and separate calendars a testing contractor uses to track recurring compliance testing. The platform runs alongside dispatch and accounting software rather than replacing them, because those tools do not carry the regulated program itself.

No. Our product is workflow software for regulated testing contractors, made by Stratum Infrastructure Inc. It has no connection to the Stratum protocol used in Bitcoin mining or to any cryptocurrency product.

No. Your team determines the requirements, review criteria, cadence, and output structure that apply. We carry that customer-defined configuration through the work, and we do not interpret requirements or give legal advice.

Request a walkthrough through Contact. We can discuss your program and agree on a time separately. How it works, the UST workflow guide, and the Pricing comparison explain the operating model before you request a call.

Start with the paid operators doing the work and the sites in scope. Then compare evidence capacity, onboarding, and owner-access availability across all six plans.

Solo is $699 per month, Team is $1,349 per month, Growth is $2,299 per month, and Regional is $3,399 per month. Enterprise and National are priced with sales, and every published number, including overage rates, is on the Pricing page.

Plans are sized by paid operator seats, sites in scope, and included evidence capacity. Larger plans include more of each, and Pricing lists the published overage rates that apply when a program runs past its included capacity.

Solo is $6,990 per year, Team is $13,490 per year, Growth is $22,990 per year, and Regional is $33,990 per year. Enterprise and National annual terms are set with sales.

Yes. Solo is sized for one operator doing the testing, and each larger plan adds seats, sites, and evidence capacity, so a small contractor starts on the plan that matches the program today and moves up when the work does.

Online purchase is not available today. Use Contact to discuss your team, sites, and plan fit. Enterprise and National begin with sales.

Yes. Facility owners you test for sign in and see current status and finished packets, nothing else. Read-only owner access is included on Enterprise and National, is available as a monthly add-on on Team, Growth, and Regional, and is not part of Solo. Ask for the add-on rate on your call.

Stored form data and attachments count toward the evidence capacity included with the selected plan. Pricing shows the included capacity and every published evidence-overage term.

Solo and Team are self-guided, Growth and Regional includes guided setup, and Enterprise and National use white-glove onboarding.

Bring the program configuration and onboarding level you are evaluating to your call, and we confirm the setup sequence and timing for your selected plan before you commit.

Plan prices, included capacity, and overage rates are published on the Pricing page. Contract length, payment terms, cancellation, and support coverage are settled on your call before purchase, so your team leaves with all four written down.

Bring the record types, formats, approximate volume, and history you need to move to a technical call, and we confirm the supported path before purchase. Do not send customer or regulated records through the public contact page.

Prepare packets from configured templates and connected records. Map collected information into configured PDF fields. Prepare configured state regulator exports from reviewed records. Customers define their requirements, review criteria, and output structure.

Name the system, the data direction, and the outcome you need on a technical call, and we confirm support for the connection before you choose a plan.

Maintain user records for the workspace. Bring the access rules your team requires to a technical call, and we confirm the supported permission model before you choose a plan.

Retention periods come from the rules your program operates under, and your team configures them. In UST testing, federal periods differ by record: 40 CFR 280.35 requires three years for specified spill, sump, and overfill testing or inspection records, and 280.36 requires one year for walkthrough records. Stored evidence counts toward the evidence capacity included with your plan.

Connect asset context, governing rules, recurring obligations, field jobs, evidence, quality control, finished packets, retained records, and recurrence in one continuous operating record. Your team defines the requirements, review criteria, cadence, and output structure. We carry those decisions through every job, and they stay yours.

Use the due-diligence topic on Contact to prepare an email with the security, privacy, or technical areas your team needs to evaluate. Do not include sensitive records or credentials.

Email support@stratuminfra.ai for a reproducible product issue. Include the affected area, steps, expected result, actual result, frequency, and impact, without sensitive records or credentials. Use Contact for a broader technical or implementation question.