Talk to us about a workload.

All inquiries go to a single address. A short, concrete description of the work is the fastest way to a useful conversation.

Contact options

What to include

Help us understand the work

  • The workload — what the process is and who performs it today
  • The inputs — repositories, document types, or systems involved, and their rough scale
  • The result — what a correct, reviewed output looks like
  • The constraints — data residency, security requirements, and timing

Please do not send confidential data or credentials in a first message.

What happens next

From first note to assessment

  1. Review. Your note is read against our scope to confirm whether the workload fits.
  2. Working session. A session with the people who own and perform the work.
  3. Written proposal. An assessment scope, deliverables, and data-handling terms, in writing.

Company

Legal name
FGGJTNBGNCR LLC
Jurisdiction
Mississippi, United States
Email
[email protected]

FAQ

Questions to settle before an assessment.

Short answers on models, data, deployment, people, stopping points, spend, and run records.

Data handling

Which models do you use?

Each step uses the smallest model that passes that step's evaluation. All model calls go through the model gateway, where routing and budgets are applied. The model providers involved in your workload are named in the data-handling terms.

Is our data used to train models?

No. Your data is used only to run and evaluate your workloads. Any training or fine-tuning on your data requires a separate written agreement.

Where does the system run?

Client-hosted in your environment, in a single-tenant dedicated environment, or as a hybrid of the two. The deployment model is chosen during the assessment, with your Security & IT contact.

What do you need from our team?

A workload owner who defines the outcome and makes the go / no-go decision at each gate; domain reviewers who help build the evaluation set and review outputs; and a Security & IT contact who approves access scopes and reviews data flows.

Can we stop after any stage?

Yes. Every gate is a decision made on written evidence by named approvers, and stopping is a valid outcome at any of them. The assessment output — workload brief, data inventory, and feasibility assessment — is usable whether or not you proceed.

How is spend controlled?

Budgets are agreed at Define and enforced at the model gateway per workspace, workload, and run. Cost is reported per accepted output.

Where do security questionnaires go?

Security questionnaires and vendor onboarding forms go to [email protected], together with the form or portal your organization uses.

Who keeps the run records?

Run records are retained according to the schedule agreed for your workload and can be exported to your SIEM or log archive. Ownership of run records is set in the written agreement.