01
The Specification
A lightweight rich-text format with openly documented, readable source. People and AI should be able to work directly with its content and formatting, independently of our cloud.
ONDC · Schemas · Examples · Compatibility Rules
The Open Foundation
An Open Standard.
Independent Software.
The standard, the software, and the service should stand on their own. We are designing Skydream so people can choose independently at each layer.
Architecture
Specification, Software,
and Providers
02
The Open Software
The document engine, clients, encryption and recovery logic, self-hostable server, and storage interfaces. The complete product should be independently usable and open to modification.
Web & Desktop · Planned Mobile · Server/API · Storage Adapters
03
The Provider
Our managed service, a server you operate, or a compatible service run by someone else. Providers should compete on service quality while preserving a supported path to leave.
Managed Hosting · Self-Hosting · Independent Providers
03 
Skydream
Cloud 
CloudflareEdge Hosting
Amazon S3Object Storage
PostgreSQLDatabase
Hosting Providers
SkydreamCloud
Self-Hosted
Server
Server
Independent
Providers
Providers
Infrastructure Options
CloudflareEdge HostingAmazon S3Object StoragePostgreSQLDatabasePlanned infrastructure choices for edge hosting, object storage, and databases.
02
Independent Applications
DriveDocsPhotosSheetsSlides
Drive
Docs
Photos
Sheets
SlidesWeb · Desktop · Planned Mobile
Document Engine
Server & Sync APIStorage Adapters
Encryption & Recovery
Server & Sync APIStorage Adapters
Encryption & Recovery
01
Open SpecificationDraft
ONDC / 1.0-draft.1
Open Native Document
1. Readable Rich Text
A lightweight text-based source exposes document content, structure, and formatting directly to people and AI.
2. Direct Source Access
AI tools should be able to read and edit the source without unpacking an archive or converting the document to another text format.
Open Source
Open source should give people practical rights: inspect the code, change it, run it themselves, and share improvements under the published license. A public repository is only the beginning.
A Complete Open Release
Our intended release includes the product’s source, self-hosting instructions, protocols, and the tools needed to validate supported behavior.
Clear Commercial Boundaries
Managed hosting can charge for storage, operation, and support. Billing and service management must not become dependencies of the open product.
Explicit Terms
Specification, software, and contribution licenses will accompany their public releases. Brand-use rules are a separate policy.
Infrastructure
Storage and Portability
Local use should remain possible without a cloud account. A self-hosted installation should include the server and the durable state needed to operate it.
Changing providers requires a complete migration: files, assets, and the information needed to recover the workspace. Storing a few objects in a personal bucket is not enough if the only usable history and index remain elsewhere.
The initial direction is our managed service and simple self-hosting, followed by more storage adapters and compatible providers. Migration and interoperability must be demonstrated before they are offered as guarantees.
Participation
Contribution and Governance
Source and Proposals
Public repositories are being prepared for code, issues, and change proposals. They will provide a durable record of review and decisions.
Community Discussion
Discussion channels should welcome questions and disagreement. Specifications and decisions should remain accessible without joining a private chat.
Published Governance
Maintainer roles, review authority, contribution rules, and routes for challenging decisions need to be defined before the process is adopted.
Independent implementers and providers are welcome in the intended ecosystem. Until the public contribution channels open, you can contact the project directly.
Contact the Project