An office suite whose documents are HTML
Open a document in a browser and it renders. Open it in a text editor and it reads. Put it in git and the diff is readable. No converter, no runtime, no format anybody has to reverse engineer in ten years.
AuraPage .aupg
Documents that are HTML, paginated by the engine your browser already has.
AuraSheet .aush
A grid where a cell can hold anything the web can draw. Not started.
AuraDeck .audk
Slides that open in any browser with no app and no converter. Shipping.
AuraBase .aubs
A database editor that is a guest in somebody else's file. Not started.
Why it is built this way
A browser engine is already a layout engine, and the most heavily optimised piece of software most people run. It handles text shaping, line breaking, tables, floats and fonts. Word processors normally reimplement all of that, which is why there are about three of them in the world.
So the document is HTML and CSS in a zip, and the pages are computed rather than stored. A change of margin does not rewrite every paragraph, and a PDF agrees with the screen by construction.
What an account is for
The apps work offline and keep working. An account covers the whole suite and buys the parts that run on our side: storage, sharing, a relay. Nothing that happens on your own machine is behind a tier, because a word processor that stops opening your own files when a card expires is not a product anybody should build.