Short answer. Plugsky serves US workloads from
us-east-1in Virginia. That is a live in-country region, not a nearest option. Private VPC, on-premises, air-gapped deployment and Riyadh Enterprise are contract-only. FedRAMP, StateRAMP, ISO 27001, SOC 2 certification and HIPAA certification are not claimed; request the current SOC 2 report under NDA and verify the period.
2027 planning guide — evidence checked 20 November 2026.
Availability at a glance
The table separates a live region from a contract-led deployment. “Contract” means the scope is agreed in writing; it is not a self-serve toggle.
| Option | Status | What it means in the US |
|---|---|---|
| Live region | live | us-east-1, Virginia. Production inference can run in-country. |
| Nearest region | live | The same Virginia region. There is no separate US fallback that is closer. |
| Private VPC | contract | Dedicated endpoint or VPC scope; network, keys and support access are confirmed in writing. |
| On-premises | contract | Customer-operated deployment; hardware and support scope sit in the contract. |
| Air-gapped | contract | Offline deployment; model bundle and update path are agreed in writing. |
| Riyadh Enterprise | contract | Enterprise option in Riyadh; not a US default and not a self-serve region. |
What a US buyer is actually buying
US buyers rarely ask only for an API endpoint. They ask where data is processed, who can access it, what happens on deletion, which subprocessors touch it, and what evidence exists. A low price does not answer any of those questions.
Plugsky's US offer is deliberately narrow: an OpenAI-compatible API in Virginia, plus contract-led private deployment for teams that cannot use a shared region. The public catalogue has 39 model IDs; the main text models serve 262,144 tokens of context. Those are product facts, not a residency guarantee.
The buyer job is to turn those facts into a file that security, legal and procurement can defend. That means mapping every data path, not just the inference call: logs, backups, support sessions, evaluation data and any human review.
The US framework: state privacy, sector rules and federal procurement
The US has no single comprehensive federal consumer privacy statute. A US buyer therefore works from a patchwork: state laws, sector regulators and the clauses attached to the contract.
State privacy laws
California's CCPA, as amended by the CPRA, is a broad state regime; Colorado's CPA is another. Both use familiar concepts: notice, access, deletion, correction, opt-out, processor contracts and risk assessments. Thresholds, exemptions and enforcement differ. Do not assume a California analysis transfers to Colorado, or to a state with no comprehensive law. Verify with counsel which states apply to your customers and employees.
Sector rules
HIPAA covers protected health information, GLBA covers financial institutions, FERPA covers education records and COPPA covers children's data. The FTC Act's unfair or deceptive practices authority sits alongside them. Plugsky offers a BAA by contract, subject to review, but is not HIPAA certified. It does not claim FedRAMP authorization or ISO 27001 certification.
Federal and state procurement
Federal buys run through the FAR: Part 12 for commercial products and commercial services, Part 39 for information technology, and agency-specific security clauses. Many agencies also expect FedRAMP or an equivalent assessment; Plugsky does not claim FedRAMP. State procurement adds its own registration, terms and security questionnaires. A self-serve plan is not a substitute for a contract vehicle.
Build the file around the DPA, the current subprocessor list, the SOC 2 report or attestation under NDA, incident-notification terms, deletion terms and the support-access model. Verify with counsel and your procurement office before relying on any of it.
How Plugsky maps to a US review
Use the product links below as evidence requests, not as proof of compliance. Each one should be read with the contract that governs your account.
- Data location: confirm Virginia processing, backups, logs and support paths. Start with data residency questions.
- Network isolation: private VPC or a dedicated endpoint is contract-led. See private VPC AI.
- No outbound path: air-gapped deployment is contract-led. See air-gapped AI.
- Key control: bring-your-own-key scope must be written into the order. See BYOK.
- Procurement evidence: request the security pack and current report under NDA through security procurement.
- Commercial path: compare pricing, read the docs, or review the sovereign AI model.
New York: finance, insurance and legal review
New York buyers are concentrated in financial services, insurance, legal, media and advertising technology. The procurement question is usually not latency to Virginia; it is whether the vendor can support confidentiality, records retention and access controls that survive a bank or law firm review. A Virginia region keeps the network path short, but the contract and subprocessor list do most of the work. Next step: give your security team the DPA and ask for the current SOC 2 report under NDA before a pilot.
San Francisco: developer speed and model switching
San Francisco and the Bay Area mix AI-native startups, SaaS, developer tools and venture-backed platform teams. Buyers optimize for time to first token, SDK compatibility and the ability to switch models without a rewrite. The practical test is a one-day OpenAI-compatible pilot against us-east-1 with your own prompts and failure cases, not a benchmark slide. Next step: run the migration check with your base URL, streaming and tool-call paths, then decide whether a private VPC is needed.
Seattle: cloud-native teams and vendor concentration
Seattle's buyer base spans cloud infrastructure, enterprise software, aerospace and retail technology. Teams often already run in US cloud regions and care about network egress, identity, logging and vendor concentration. Virginia is a short domestic hop, but procurement will ask how support staff access data and where logs are stored. A short domestic path helps, but the bigger question is whether the vendor's support model creates an overseas access path. Next step: request an architecture review that maps your VPC, key management and log retention to the Virginia deployment.
Austin: public sector and regulated growth
Austin combines technology companies, state government, healthcare and education. Public-sector and regulated buyers bring rules that startups do not: security questionnaires, accessibility terms, records retention and sometimes state residency preferences. Texas has its own consumer privacy law, the TDPSA, and sector and contract terms still apply. A public-sector buyer may also need a contract vehicle, accessibility documentation and a records schedule that a startup sales team does not have ready. Next step: ask for the security pack and a contract review before assuming a state agency can buy from a self-serve plan.
Local search phrases to validate
These are research prompts, not published keyword targets. Validate with a native reviewer; not published as localized copy. No volume, difficulty or ranking data is claimed.
| Phrase | Likely intent | Validation note |
|---|---|---|
| private AI API United States | Vendor discovery | Separate US-only vendors from global vendors with a US region. |
| US-hosted AI API | Residency | Check whether the searcher means hosting, incorporation or support. |
| data residency AI API US | Compliance | Look for state-specific and sector-specific variants. |
| OpenAI-compatible private API | Migration | Check developer forums and SDK documentation queries. |
| enterprise LLM API Virginia | Region | Likely low volume; validate before creating copy. |
| AI API for financial services | Vertical | Watch for regulatory wording such as model risk and audit. |
| state government AI procurement | Public sector | Check state contract language, not only marketing pages. |
What we did not verify
We did not verify FedRAMP, StateRAMP, an agency authority to operate, ISO 27001, SOC 2 certification or HIPAA certification; none is claimed. We did not verify customer logos, case studies or city references, and we did not measure latency from New York, San Francisco, Seattle or Austin. We did not complete a state-by-state legal analysis or review your DPA, security questionnaire or contract. We cannot confirm that us-east-1 satisfies every contractual data-location requirement; the signed terms govern. Verify with counsel and your procurement office.
FAQ
Does Plugsky have a US data region?
Yes. Plugsky's US region is us-east-1 in Virginia. It is a live region, not a nearest-region substitute.
Is US data guaranteed to stay in the United States?
Processing can run in us-east-1 Virginia, but “guaranteed residency” is not claimed. Backups, logs, support access and subprocessors must be confirmed in the contract for your workload. Verify with counsel.
Is Plugsky FedRAMP authorized?
No. FedRAMP authorization is not claimed. Federal and state buyers should request the current SOC 2 report or attestation under NDA, verify the period, and run their own assessment.
Can Plugsky sign a BAA for HIPAA workloads?
A BAA is available by contract, subject to review. Plugsky is not HIPAA certified. Confirm the scope, model path and data flows with counsel before handling protected health information.
Which state privacy laws apply to my business?
It depends on your customers, revenue, data volume and sector. California's CCPA/CPRA and Colorado's CPA are two examples, not a complete list. Verify with counsel; Plugsky does not provide legal advice.
Can we get a private VPC in the US?
Yes, private VPC or a dedicated endpoint is available on contract terms. Scope the network, key management, logging and support access in writing before you assume isolation.
Can we run Plugsky air-gapped?
Air-gapped deployment is contract-led. Confirm the model bundle, update path, hardware requirements and support model in the contract; it is not a self-serve option.
How do we start a US pilot?
Start on the free plan or a paid plan, point the OpenAI-compatible SDK at the US endpoint, and test your own prompts. For a private deployment, request an architecture review with your security and procurement leads.
Sources
Last checked 20 November 2026. Official pages were reviewed on that date; legal and procurement summaries are for orientation, not advice.
- California Attorney General, California Consumer Privacy Act (CCPA) — checked 20 November 2026.
- Colorado Attorney General, Colorado Privacy Act (CPA) — checked 20 November 2026.
- U.S. General Services Administration, Federal Acquisition Regulation (FAR) — checked 20 November 2026.
- Federal Trade Commission, Privacy and Security — checked 20 November 2026.