/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Box teams up with Google to become a 3rd-party storage option for Google Docs, Sheets, and Slides; Box-stored content will be searchable via Google Springboard

Darrell Etherington / TechCrunch :

TechCrunch Darrell Etherington

Context & Ripple Effects

This deal extends a two-year courtship: Google first brought Box storage onto Chromebooks in 2015, and Box responded by repositioning itself as a developer substrate with Box Platform rather than just a file-sharing app. Now the relationship deepens from device-level sync into the document-editing core itself.

The timing is pointed — Google had just opened Team Drives to early adopters, its own answer to enterprise file sharing. Letting Box sit underneath Docs, Sheets, and Slides means Google is betting its editors can be the work layer even when the repository belongs to a rival.

First-order effects

  • Enterprise customers running on Box gain native creation and editing of Google documents against Box-stored files, removing the migration pressure that would otherwise force a choice between Box storage and Google's editors.
  • Google Springboard search now indexes content living in Box, giving Box customers discovery across their repository without leaving Google's surface.

Second-order effects

  • The integration sets a template Google repeats with Dropbox in 2019 via G Suite support for working on Google files inside Dropbox — once one rival storage provider gets editor access, others must demand parity or lose collaborative-document workloads.
  • Box's differentiation shifts toward being the neutral enterprise repository that plugs into every editing suite, pressuring Microsoft's Office-plus-OneDrive bundling on accounts where Google editors are preferred.

Third-order effects

  • If the pattern holds, cloud editors fully decouple from storage: Google keeps expanding this openness — business-grade Drive File Stream, Team Drives, and Vault on its own side, and eventually smart chips pulling third-party app data directly into Docs — making the document canvas the durable lock-in rather than where files live.
  • Enterprise content platforms compete on governance, security, and API reach instead of viewer/editor bundles, consolidating the market around repositories that integrate everywhere versus suites that own the whole stack.

The trend: Cloud productivity editors are becoming storage-agnostic work surfaces, with Google systematically letting rival repositories like Box and Dropbox plug into Docs, Sheets, and Slides.