Frequently asked. Honestly answered.

The pricing page and estimator show illustrative planning amounts and configurations. They are not quotations or approved offers. An engineer confirms scope, capacity, dependencies and commercial terms in a written proposal.

Confirm bandwidth allowances, egress treatment, overage handling and any third-party network charges in your written proposal. The website does not establish a no-egress-fee commitment.

Contract duration, renewal, cancellation, notice periods and any discounts must be agreed in writing. No default term or cancellation right is established by this FAQ.

Enterprise engagements require a scoped proposal. Share your procurement requirements, scale and service expectations so the proposed work and commercial terms can be reviewed.

Confirm available payment methods, billing arrangements, fees and purchase-order requirements during procurement. Marketplace checkout availability must be verified separately; this FAQ does not authorize a purchase.

A senior engineer confirms scope, dependencies, review gates, and compliance obligations before committing to a schedule. AI accelerates the work, but the signed scope—not a blanket turnaround claim—is authoritative.

Agree the deliverables, hosting responsibilities, security controls, backup and recovery requirements, documentation and post-launch support in the statement of work. Services are included only where explicitly scoped.

Confirm ownership, licences, third-party restrictions, repository access and exit or handover arrangements in your agreement before work begins.

Share the stack, dependencies, licences and operational requirements for review. Container compatibility is one consideration; suitability, support and migration effort require an engineering assessment.

Ultiblob operates multi-region private cloud infrastructure. Confirm workload placement and resilience requirements during scoping.

Ask your contact about any available facility review or visit process. Access, scheduling, confidentiality and security requirements must be confirmed in advance.

Our current private cloud locations are in the United States. Discuss any additional location or jurisdiction requirements before selecting a service.

Specify which compute, network and storage resources must be dedicated or isolated in the proposed design. Tenancy and resource-sharing boundaries should be documented and verified for the selected service.

Discuss hardware ownership, compatibility, location, support and operating responsibilities during scoping. Any arrangement depends on an agreed design and service scope.

Confirm any BAA requirement and whether an appropriate agreement can be executed before sharing PHI. This website does not establish contractual coverage or compliance.

No SOC 2 report or attestation is currently substantiated for publication. Share your evidence requirements during security review so any gaps are explicit.

Payment-data scope, responsibilities and validation requirements must be assessed for each engagement with your qualified advisers. No PCI certification or compliance status is claimed here.

Confirm the selected AI providers, retention, training settings and contractual terms before sending customer data. Do not enter sensitive information into the public website assistant.

Identify key ownership, custody, access, rotation and recovery requirements during security review. Confirm whether the selected service can support them; no tier-wide BYOK or HSM availability is promised here.

Share your model, memory, throughput and isolation requirements. Hardware selection, availability, commercial terms and delivery times must be confirmed in a written proposal; this page does not reserve capacity.

Agree the model providers, authentication, data handling, usage limits, monitoring and integration responsibilities in the service scope. Any caching benefit or cost estimate must be measured for your workload; no percentage saving is promised.

Provide the model and licence, intended use, data requirements and performance targets for assessment. Runtime compatibility, hardware capacity and support must be validated before committing to a deployment.

Confirm support hours, contact channels, severity definitions and response commitments in the agreed service scope. This website does not establish an SLA.

Discuss who monitors your systems, who investigates alerts and who can approve or execute a change. Any automation, access limits and escalation process should be documented for your engagement.

Confirm your operational contacts, escalation path and review schedule during scoping. Named staffing arrangements must be agreed explicitly.

Agree how incidents are reported, prioritized, escalated and communicated. Response targets, remediation authority and post-incident reporting belong in the service agreement.