New partnership. Open estate.
VeUP joined the OpenAI Partner Network in July 2026 for referral, co-sell and delivery services. OpenAI models already run in production inside estates VeUP operates — and the migration onto Amazon Bedrock is where most of that work is heading.
The engagements whose records name these models.
OpenAI is in production in the VeUP estate today, running in parallel with Claude and Gemini. The engagement below is the published record of it: one metered gateway in front of every provider, and a model channel moving onto Amazon Bedrock so multi-provider usage consolidates onto a single AWS bill.
OpenAI runs in production alongside Claude and Gemini — the OpenAI embedding model backs the product's vector search over self-hosted pgvector. VeUP put a single metered gateway in front of all three providers and is moving the model channel onto Amazon Bedrock, so multi-provider usage consolidates onto one AWS bill and a provider change becomes configuration rather than code.
OpenAI runs in the product's application layer, written by the customer's app-dev partner against the Lambda and queue contracts VeUP defined. What VeUP built is the governance underneath it: every AI prompt and every AI recommendation is a first-class governed event — flagged AI-generated at ingestion, attributed to the model that produced it, bound to a lawful basis, and captured in an audit vault queryable in Amazon Athena. So OpenAI output is not just generated, it is provable, consent-checked and erasable.
Referral, co-sell, and delivery services.
The same delivery machine that runs the Claude and open-weight work, pointed at OpenAI models — with the model still chosen by benchmark, and the workload still landing on AWS.
- Referral and co-sell motions alongside the AWS Advanced Tier services practice.
- Delivery services: evaluation harness, gateway metering, guardrails, and observability from day one.
- The same bake-off protocol — an OpenAI model earns the workload on a labelled dataset or it does not get it.
- Accounts in the estate below are where OpenAI models were discussed on recorded calls, nothing more.
33 accounts where OpenAI is on the table.
These are customer accounts VeUP runs where this model family came up on a recorded customer call — architecture sessions, evaluations, roadmap conversations. That is engagement evidence, not a statement that the customer runs these models in production. Promotion to a production claim means a published case study, which is what the section above holds. 10 of these 33 are named here because they already have one. Every other row stays anonymized — including customers who do have a published case study but have not agreed to be named, who appear by description only.
- Identity held on fileTelecommunicationsBuildIgniteSellOperate28 AWS accounts
- An AI meeting-intelligence SaaS companySoftware DevelopmentBuildIgniteSellOperate13 AWS accounts
- Identity held on fileInformation Technology and ServicesSellOperate11 AWS accounts
- BrontoSoftware DevelopmentSellOperate10 AWS accounts
- Identity held on fileComputer SoftwareBuildSellOperate9 AWS accounts
- Cluster Systems (product: ClusterPOS)Software DevelopmentBuildIgniteOperate9 AWS accounts
- FerootComputer & Network SecuritySellOperate9 AWS accounts
- Identity held on fileComputer SoftwareSellOperate9 AWS accounts
- Identity held on fileConstructionSellOperate8 AWS accounts
- A multi-tenant GRC SaaS providerSoftware DevelopmentSellOperate6 AWS accounts
- HopsyComputer SoftwareBuildSellOperate5 AWS accounts
- Identity held on fileElectrical/Electronic ManufacturingIgniteOperate4 AWS accounts
- A Canadian digital-risk-protection cyber-security ISVComputer & Network SecurityBuildSellOperate4 AWS accounts
- Identity held on fileVenture Capital & Private EquitySellOperate4 AWS accounts
- InteliGems LabsInformation Technology and ServicesSellOperate3 AWS accounts
- SalesNOW (Interchange Solutions Inc.)Software DevelopmentSellOperate3 AWS accounts
- Identity held on fileSoftware DevelopmentSellOperate3 AWS accounts
- A consumer connected-home-security IoT platformComputer & Network SecuritySellOperate2 AWS accounts
- Identity held on file—Operate2 AWS accounts
- Identity held on fileSoftware DevelopmentIgniteSellOperate2 AWS accounts
- TenderdComputer SoftwareSellOperate1 AWS accounts
- AllstacksComputer SoftwareBuildSell0 AWS accounts
- Identity held on fileSoftware DevelopmentBuild0 AWS accounts
- Identity held on fileComputer SoftwareIgniteSell0 AWS accounts
- Identity held on fileManagement ConsultingSellOperate0 AWS accounts
- Identity held on fileSoftware DevelopmentSell0 AWS accounts
- Identity held on fileComputer SoftwareBuildIgniteSell0 AWS accounts
- MyCena Security Solutions—Sell0 AWS accounts
- Identity held on fileBiotechnologyIgnite0 AWS accounts
- Identity held on fileHospital & Health CareBuild0 AWS accounts
- A travel-technology company building a governed traveler-data platformLeisure, Travel & TourismBuildIgnite0 AWS accounts
- Identity held on file—Build0 AWS accounts
- ZenhubDocumentedProgram DevelopmentBuild0 AWS accounts
Every account here is a VeUP customer where this family is in the work. The chips are the engagement motions VeUP runs at that account — Build means VeUP builds and operates there, Ignite that VeUP funds and resells the estate, Sell and Marketplace the co-sell and listing motions. Operate marks the estates where VeUP is the AWS payer of record. Accounts are resolved from the customer registry and the meeting archive on participant email domain. Counting conversations is not counting deployments — the number is here as scope, never as a claim. Linked AWS accounts describe estate size, not spend.
