what is OneBucket?
OneBucket™ is a control plane that gives your applications, developers, and AI agents unified access to all of your data — across cloud, on-premises, and the edge — through native MCP and S3 interfaces. It's built on our Adaptive Data Fabric™, which operates at the API layer to route, cache, and move data under policy you control.
how is this different from migrating my data to the cloud or a data lake?
Our approach is orchestrate, don't migrate. Instead of copying your data into a new system before AI can use it, OneBucket connects to data where it already lives and presents it as one logical bucket. There's no lift-and-shift project, no duplicated storage, and no rearchitecting — you keep your existing systems and policies in place.
do i need to copy or move my data?
No. OneBucket reaches your data in place. Because the Adaptive Data Fabric™ works at the API layer, it's stateless and lightweight — applying policy-driven routing and caching without forcing copies. When data movement is useful (for performance or locality), it happens under the policies you define, not as a prerequisite to getting started.
which clouds and storage providers does OneBucket support?
AWS S3, Azure, and Google Cloud, plus on-premises storage, the edge, and air-gapped environments. It also connects to platforms like Snowflake and Databricks. Any provider you connect becomes part of the same unified namespace.
how do ai tools and agents access the data?
Through two native interfaces: MCP (Model Context Protocol) for AI agents and assistants, and the S3 API for applications and tooling that already speak S3. Your AI sees one consistent endpoint regardless of where the underlying data physically lives.
which endpoints do i connect to?
OneBucket runs in multiple regions, each exposing an
S3 endpoint and an
MCP (core) endpoint — point your apps and AI at the region closest to your data:
- sjc · san jose — S3:
s3.cluster7.onebucket.io · MCP: mcp-core.cluster7.onebucket.io - iad · ashburn — S3:
s3.cluster8.onebucket.io · MCP: mcp-core.cluster8.onebucket.io
how does setup work?
Three building blocks: Core Keys — the provider-abstracted credential your apps use to authenticate to OneBucket; Endpoints — connections to your storage providers, each holding its own provider credentials; and Policies — a short wizard that maps Core Keys to your real buckets, with controls for read/write/delete, replication, compression, region, and sync quorum. Most teams connect a first environment in minutes.
does my data stay secure and in place?
Yes. Provider credentials live with their Endpoint and aren't exposed to applications, which authenticate only with a Core Key. Access, replication, and movement are governed by the Policies you set — so you unlock data for AI without compromising compliance or giving up control over where data resides.
can OneBucket run on-premises or in an air-gapped environment?
Yes. OneBucket runs as SaaS, inside your VPC, on-premises, or fully air-gapped — so it fits environments with strict data-residency or isolation requirements.
what results can i expect?
It depends on your environment, but as one example, Rivet Industries used OneBucket to increase GPU utilization by 30%, drive AWS egress costs to roughly zero, and ship faster — with zero compliance compromise. The premise: less than 10% of enterprise data is reachable by AI today, and OneBucket is built to unlock the rest.
how do i get help or support?
how do i get started?