Beta
Known limitations
Your data can be lost, and there is no backup
Spheromni has no backups. Not untested backups — none are configured. If data is lost, whether by a fault, by a mistake, or because you deleted something, it cannot be recovered. Deleting your account is immediate and permanent, with no grace period and no copy anywhere.
Keep your own copy of anything you cannot afford to lose. This is the single most important sentence on this page.
Almost nothing is monitored, and nothing raises an alarm anyone receives
There is no external monitor that probes Spheromni from outside, no uptime history, no log retention beyond what the hosting platform keeps by default, and nothing that pages, emails or notifies anyone when something breaks. If Spheromni breaks, somebody finds out by looking at it or by being told. The status page runs one live check when you open it and keeps no history.
There is now a staff-only overview inside the product that counts, for the one server instance a member of staff happens to load it on and only since that instance started, how often each part of the product has succeeded or failed, and groups opt-in error reports by which build they came from. It also lets an operator turn on a manual incident banner on the status page by hand. None of that is a monitor: it keeps no history, it does not add up across servers, nothing evaluates it on a timer, and it reaches nobody — it is numbers a member of staff sees only while they are looking at that page. Real monitoring, uptime history and automatic detection remain future work.
Error reports exist only for accounts that turned them on, they carry a message and a page path and nothing else. Nothing pushes them anywhere; the only thing that reads them is the by-build count above, which is a bare number per build and carries none of the message text.
Spheromni sends you nothing outside the product, ever
No email, no push notification, no SMS. Not for a new sign-in, not for a security event, not when something breaks, and not to send you an invite code. There is now an in-product notification center — a bell inside your workspace that shows when somebody answers your feedback or your privacy request, or invites you to a share — but it lives entirely inside the product: nothing about it leaves your browser, and when you are not here, nothing reaches you anywhere else. Every answer Spheromni has for you still exists somewhere you have to open and look at.
The beta gate is a front door, not a lock on every room
Access to the beta is checked when the workspace loads and when you sign in. Your files, your Google Drive connection, anything you have shared or been invited to, presence, community, commerce, your subscription, the store, and the companion's settings all now check eligibility again on every request of their own, not only at that door. It is deliberately not re-checked by every individual request across the whole product: routes that only manage the account you already have — deleting it, exporting it, your consent choices — do not check beta eligibility, because whether you may use the beta is a different question from whether you may manage an account you already hold. Nobody gets in without signing in, and nobody sees anybody else's data — that is enforced separately and always. The invite gate itself is stated as a front door rather than described as a security boundary it is not, and per-request enforcement has landed for the surfaces that hold your data.
The workspace's own boot check still fails open: if the eligibility check cannot be made because something is down, the workspace loads rather than locking everybody out. That is the deliberate trade, and it is the reason an outage does not become a lockout. The surfaces that now check eligibility on every request take the opposite trade instead: a check that cannot be made there answers unavailable rather than letting the request through.
The adults-only rule is stated, not verified
Spheromni asks you to confirm that you are an adult and records your answer. It collects no date of birth and performs no age check of any kind, so the restriction rests on what people tell it.
Single region, single instance
Spheromni runs as one application instance in one region. There is no failover and no second copy. Some protections — the limits on how often a request can be repeated, for example — are held in memory, one instance at a time, by default, and reset whenever it restarts or is redeployed. Where a shared counter store is set up for them instead, those limits are counted across every instance together for as long as that store answers, and fall back to the same one-instance behaviour the moment it does not.
Nothing can be bought
There is no payment path anywhere: no prices, no checkout, no card details asked for or held, and no charge has ever been made. Plans exist and every one of them gives the same thing. Nothing in the store costs anything and installing an application is not a purchase.
Application permissions are now checked, with one honest limit
Every application tells you what it declares access to before you install it, and you can review that afterwards. Since this release, the server checks that record whenever a request says which application it comes from: what was declared, what you have granted, and what you have revoked, and you can revoke or restore individual capabilities in Settings, under Privacy. Any account can now accept the Developer Agreement and submit an application of its own for review; nothing submitted is visible to anyone else until a person approves it, and every application actually published in the store today is still built by Spheromni. The honest limit has narrowed but not vanished: an application run inside the new sandboxed runtime cannot speak for anyone but itself, while an application rendered directly into the workspace still shares its origin, so for those "which application a request comes from" remains the product's own word. Two declared capabilities — the microphone and browser storage — happen entirely inside your browser, where no server check can see them, and remain disclosures.
Limits inside the product
- Files are text only, up to one megabyte each.
- Google Drive is read-only, one page of results deep, and Spheromni notices changes only when a folder is listed.
- There is no version history for a file, and no per-item history in Tasks or Calendar.
- Lists that are cut short say so, but there is no way to page through the rest.
- There is no way to unlink a sign-in provider from inside the product.
- There is no copyright complaint route, no notice-and-takedown procedure and no designated agent.
- Voice uses your browser's speech recognition, so your browser may send the audio to its own vendor. Spheromni never receives audio.
The legal documents are drafts
Every legal page on this site, including the Beta Terms and the Beta Privacy Notice, is a draft prepared for review by qualified counsel. With one narrow exception, none is in effect, several carry unresolved placeholders, and there is no mechanism to ask you to accept a changed version. The exception: the Developer Agreement is now asked for and its acceptance recorded — that is what opens the app-submission surface — and a changed version of that one document does require a fresh acceptance before you can keep submitting. Its text is still a draft for counsel like every other.
No independent security test has been performed
Preparation for one exists; the test itself has not happened. Nothing on this site claims otherwise.
The beta may end, and it may be reset
Features appear, change and are removed. A feature behind a switch may be withdrawn without notice, and data associated with it may not survive that. The Beta Terms say the same thing in the language of a document; this page says it plainly.