AI-coding · AWS
Poolside
Poolside builds and trains proprietary foundation models via its internal **Model Factory** (Titan training stack on a ~10K GPU cluster, Apache Iceberg data layer, Kubernetes orchestration) and then deploys those models and agentic systems fully inside customer VPCs/on‑prem through the Poolside Platform, with additional distribution via AWS Bedrock and Trainium-backed inference.[1][2][7][8][9][5][6][11] The production architecture is therefore a proprietary, Kubernetes-based ML/agent stack running on AWS (and customer infrastructure) with an Iceberg-centered data plane and tightly integrated model training, evaluation, and deployment pipelines.[1][2][7][8][9][11]
Foundation proximity: Native (own / self-hosted weights)
Foundational models & how they consume them
PrimaryLaguna S· Poolside (self-hosted / owns weights) · Native (own / self-hosted weights)
SecondaryMalibu· Poolside via Amazon Bedrock · Cloud-hosted (Bedrock/Vertex/Azure)
TertiaryPoint· Poolside via Amazon Bedrock · Cloud-hosted (Bedrock/Vertex/Azure)
Cloud & datastore
AWSApache Iceberg (central data/experiment layer)Object storage over Iceberg (likely S3-compatible, inferred from AWS + Iceberg usage)Kubernetes-native config/state stores (e.g., etcd; inferred from 'stacked under a single Kubernetes orchestrator')Compliance
Enterprise-grade, in-VPC / on-prem isolation (docs + platform marketing)Air‑gapped deployment support (AWS re:Invent talk)Customer-owned VPC / data residency controls (docs)No explicit public claims of SOC 2 / ISO 27001 / HIPAA in available materialsSimilar companies
MagicTabnineCognition (Devin)LovableWindsurf (Codeium)Others that build on proprietary / self-built models
Abnormal SecurityAbridgeAdobeAI21 LabsAleph AlphaAmbienceExplore
FAQ
Does Poolside use a foundational AI model?
Poolside uses Laguna S, Malibu, Point (Native (own / self-hosted weights)).
What cloud does Poolside run on?
Poolside runs on AWS.
What database does Poolside use?
Poolside uses Apache Iceberg (central data/experiment layer), Object storage over Iceberg (likely S3-compatible, inferred from AWS + Iceberg usage), Kubernetes-native config/state stores (e.g., etcd; inferred from 'stacked under a single Kubernetes orchestrator').
How close does Poolside run to the foundational model?
Poolside is Native (own / self-hosted weights) — close to the metal, so cheaper tokens and more control over outputs.
Sources
poolside.ai ↗Also on the map
← Full orbit map (260 companies) · Score your own stack →
Architecture inferred from public sources · confidence medium · verify before betting on a detail.