Skip to main content

The New NuQloud: Six Months of Better Access, Safer Publishing, Easier Collaboration, and More Personal Control

This is a historical announcement. For changes reviewed through October 29, 2026, see the October documentation update and current feature availability. Statements below describe their original reporting period and do not establish a provider's current rollout.

Global community announcement — September 14, 2026
Changes covered: March 14 through September 14, 2026

Over the last six months, NuQloud has grown from a connected cloud workspace into a much more complete home for everyday collaboration and Qortal-powered tools. The changes are not limited to a new look. They improve how you sign in, manage decentralized accounts, publish files, use decentralized apps, collaborate with other people, understand your service, recover important credentials, and move between devices.

This announcement explains the changes in user terms: what changed, what it does, and what you can do with it.

Availability can vary by NuQloud provider, server plan, enabled apps, and rollout schedule. If an item described here is not visible on your cloud yet, ask your provider or server administrator whether it has been enabled or whether your instance needs to be updated.

The Short Version​

You can now:

  • use a redesigned NuQloud Dashboard that works better on desktop and mobile;
  • follow built-in setup guides and resume them later;
  • sign in with a NuQloud Authentication File, including a simpler first-device and returning-device experience;
  • link and use more than one Qortal account;
  • manage native QORT and supported foreign-coin wallets from compatible NuQloud/Q-App flows;
  • publish files and folders to QDN through a clearer, safer queue;
  • see whether published content is current, changed, or still waiting to publish;
  • use private, sharing-key-based encryption with compatible decentralized apps;
  • install NuQloud as a desktop web app and connect supported mobile and desktop clients;
  • personalize light, dark, and color themes while administrators retain sensible accessibility and policy controls;
  • use improved purchasing, package, storage, billing, and account-status information;
  • work with newer collaboration tools, including NuQloud Scrum, cross-cloud Talk file sharing, NuQloud AI, and the NuQloud World preview where enabled;
  • benefit from a large set of reliability, privacy, upgrade, and security improvements behind the scenes.

1. A New Dashboard Built Around What You Need to Do​

The NuQloud Dashboard has been substantially redesigned. Instead of presenting one long technical control panel, Dashboard V2 organizes account information, setup, services, purchasing, notifications, and decentralized tools into clearer workspaces.

What changed​

  • A new responsive Dashboard V2 layout now provides consistent navigation across its sections.
  • Mobile users get a compact, sticky Menu selector instead of an overflowing row of tabs.
  • Node, connection, account, and package information remains available while moving between Dashboard sections.
  • Storage information now reflects the user's assigned quota more reliably.
  • Package and add-on information comes from the connected service catalog, reducing stale or misleading plan displays.
  • Purchase buttons, billing errors, active-package states, and service details use clearer language.
  • Administrators and eligible delegated operators can reach the appropriate management workspace directly from Dashboard V2.
  • Q-Apps are now labeled Decentralized Apps in NuQloud mode.

What you can do​

Open the NuQloud Dashboard to see your linked decentralized accounts, storage, current service package, available add-ons, announcements, activity preferences, and setup progress. On a phone or narrow window, use Menu to move between Dashboard sections.

The Dashboard also provides direct access to authentication-file downloads, account management, publishing-credit requests, decentralized apps, and provider-specific purchase or support actions when those services are configured.

2. Guided Setup That Remembers Your Progress​

NuQloud now includes a built-in Guides hub and an interactive first-use walkthrough. It is designed to help people set up the service without already knowing the underlying Nextcloud or Qortal terminology.

What changed​

  • New-user guidance can start automatically on first use.
  • Guide progress can be completed, hidden, snoozed, and resumed.
  • The guide highlights the relevant part of the interface instead of sending users through disconnected instructions.
  • Download actions remain available long enough to save required files more than once.
  • The guide adapts its recommendations to the device being used.
  • A searchable in-product guide library now covers account creation, desktop and mobile access, file sync, migration from another cloud, Talk, Mail, Contacts, Calendar, appointments, Deck, Notes, decentralized publishing, Decentralized Apps, Q-Mail, security, recovery, and troubleshooting.
  • A support knowledge base now uses the same validated user procedures, helping support responses stay consistent with the product.

What you can do​

Start with the Dashboard guide, complete one task at a time, and return later without losing your place. For the best everyday setup, install the NuQloud PWA on your computer, save your authentication backup, and optionally connect the compatible desktop Files client. On mobile, NuQloud Talk is recommended for chat and call notifications; the PWA and Files app can then be added for wider access.

3. Simpler Sign-In and Stronger Account Continuity​

NuQloud's sign-in system has moved toward a decentralized, passwordless-first model. The goal is to let your NuQloud Authentication File and its password establish your identity on a new browser while keeping returning sessions convenient and secure.

What changed​

  • New accounts can be created through invite links and tokens with a smoother first-login handoff.
  • The sign-in page more clearly explains Authentication File and magic-link options.
  • Pressing Enter can submit the magic-link request where that flow is enabled.
  • Saved accounts are retained when switching between supported sign-in modes.
  • After a successful first sign-in, encrypted browser-side authentication data can support later sessions on that browser.
  • Session refresh and restart handling has been hardened so routine service restarts are less likely to disconnect active users.
  • Refresh-token lifetimes and OIDC browser-session handling were improved.
  • Account recreation and server upgrades now preserve sign-in configuration more reliably.
  • Sensitive values are redacted from OIDC logs.
  • The standard compatible login form can be exposed by administrators for preparation or recovery scenarios, but decentralized sign-in remains the intended primary path.

What you need to know​

Your NuQloud Authentication File and its password are important. You may need them for the first sign-in on a new device or browser, or after clearing browser data. Keep a protected copy outside your NuQloud cloud. Do not publish it or place it in a public share.

Magic-link availability depends on provider configuration. A magic link helps complete an approved sign-in; it does not make your backup practices unnecessary.

4. Multiple Decentralized Accounts and Broader Wallet Support​

NuQloud account management now supports more real-world Qortal use. You are no longer limited to treating one linked account as the only account you may need.

What changed​

  • Multiple Qortal accounts can be linked and managed from one NuQloud user account.
  • Backup-file import and drag-and-drop are the primary linking path, with seed-phrase import available where supported.
  • Linked-account lists, current-account selection, unlinking, and backup actions were consolidated into a more understandable account area.
  • Qortal account backup files can be downloaded or saved into private NuQloud Files storage.
  • Wallet confirmation prompts were made less repetitive while a wallet is already unlocked.
  • Foreign-wallet discovery, derivation, balances, transaction history, and sends are supported for compatible coins and Q-Apps.
  • The same high-risk approval rules now apply consistently to supported spending transactions.

What you can do​

In your connected-account settings or Dashboard account area, import an existing backup, link another account, switch the active account used by compatible services, view balances and history, create a fresh backup, or unlink an account you no longer want attached.

Compatible decentralized apps may request supported foreign-coin operations. A foreign-coin send still requires an unlocked active wallet and an explicit approval. Availability depends on the coin, the connected Qortal services, and the app making the request.

5. Safer, Clearer Decentralized Publishing​

Publishing through NuQloud Files has received one of the largest groups of improvements. Ordinary cloud storage and QDN publishing remain separate: saving a file in NuQloud does not publish it until you choose the publishing action.

What changed​

  • Files and folders can be selected for QDN publishing from the NuQloud web/PWA Files interface.
  • Multi-file and folder publishing now preserves nested paths more reliably.
  • A publishing queue handles work that cannot finish immediately, including jobs waiting for a wallet unlock.
  • The queue viewer shows pending and failed work, allows editing where supported, retries eligible jobs, and clears obsolete failed jobs when dismissed.
  • Cost estimation and confirmation information are calculated before publishing.
  • Notifications are richer and publishing counts are more accurate.
  • Files show current, stale, and unpublished states. Folder indicators can also show that published or changed items exist deeper in the folder.
  • Q-Manager-compatible private filesystem manifests are merged instead of carelessly replaced.
  • Compatible apps can encrypt and decrypt content with sharing keys.
  • Private file-index updates support encrypted/private publishing workflows.
  • Deletion uses the QDN overwrite/tombstone model rather than pretending decentralized copies behave like ordinary cloud files.
  • Mobile layouts, buttons, icons, and post-publish navigation were repaired and simplified.

What you can do​

In NuQloud Files on the web or in the PWA:

  1. Open a file or folder's action menu.
  2. Choose the QDN publishing action.
  3. Review the mode and estimated cost.
  4. Confirm the request and unlock your decentralized account if prompted.
  5. Use the queue and status indicators to follow progress.

If a published file changes afterward, it becomes stale until you publish it again. Public QDN publishing should be used only for content you intentionally want public. Private publishing encrypts content, but you must still protect the relevant keys and understand that some resource metadata may remain visible.

Deleting the cloud copy does not automatically erase every previously published decentralized copy. Always review the publishing mode and resource behavior before handling sensitive information.

6. Decentralized Apps Are Easier and Safer to Use​

The embedded Q-App experience is now presented as Decentralized Apps and includes better browsing, loading, approval, and troubleshooting behavior.

What changed​

  • A gallery and optional full-browser view provide easier access to administrator-approved apps.
  • Built-in controls include back, reload, address/go, open in a new tab, and close.
  • qortal:// links are handled more consistently.
  • QDN and gateway loading failures have clearer fallback behavior.
  • Initial-load and route issues that could leave an app blank were addressed.
  • The gateway passes theme information so compatible decentralized apps can better match NuQloud.
  • Sharing-key encryption/decryption requests are available to compatible apps.
  • A refined debug dock can be enabled for troubleshooting without exposing it to everyone by default.
  • Administrators can control the approved app list, display order, icons, full-browser availability, and debugging options.

Approval protection​

NuQloud adds an extra confirmation for high-risk requests such as sending QORT or supported coins, signing transactions, registering names, trading or asset actions, deployments, polls/votes, and large publishing batches. The confirmation should appear only when the action requires it, rather than repeatedly interrupting low-risk browsing.

Only approve a request when you trust the app, understand the action, and initiated it yourself. Cancel unexpected requests.

7. A More Personal—and More Accessible—NuQloud​

NuQloud now has a dedicated branding and theme layer that reaches beyond the Dashboard. The visual update includes meaningful user controls, not just new colors.

What changed​

  • Cloud-wide NuQloud styling can cover the shared interface and compatible app surfaces.
  • Users can choose System, Light, or Dark appearance.
  • New Ocean, Orchid, and Ember palettes provide additional color choices with matched light and dark tokens.
  • Advanced Theming allows personal, validated visual overrides where the administrator permits them.
  • A user can remove personal overrides and return to the instance defaults at any time.
  • Nextcloud's native high-contrast, reduced-motion, and dyslexia-friendly controls remain available.
  • Administrators set the allowed policy and default experience; an optional NQ_Admin delegate can narrow approved choices but cannot override the built-in administrator's policy.
  • Administrator-enforced theme locks are honored.
  • Shared email envelopes, login surfaces, Dashboard V2, and cloud-wide branded areas now align more consistently.
  • Full-width and responsive settings layouts fix cramped or clipped theme controls.

What you can do​

Open Personal settings → Appearance and accessibility to choose System, Light, or Dark mode and retain the accessibility options you rely on. If Advanced Theming is available, choose an approved palette and personal options there. These settings apply only to your account; removing them returns you to your server's defaults.

8. Purchasing, Plans, Storage, and Account Management​

The service and account areas have been connected more closely to live provider information.

What changed​

  • Plans and add-ons are synchronized from the provider connector instead of relying on a fixed list embedded in the Dashboard.
  • Active packages and assigned packages are labeled more accurately.
  • Checkout can begin with the account email while still clearly allowing an authorized correction where the provider supports it.
  • Package linking, order and service status, invoice detail, payment errors, storage assignment, and quota presentation were improved.
  • Purchase links use navigation that is less likely to be blocked as a pop-up.
  • If live catalog synchronization fails, NuQloud avoids presenting stale invented packages and can offer a provider contact action instead.
  • Provider announcements can be refreshed in the Dashboard.
  • Administrators and authorized service operators gained better automation for account creation, entitlement sync, package assignment, storage, invoices, and service status.

What you can do​

Use the Dashboard's purchases or service area to review the package currently attached to your account and the plans or add-ons your provider makes available. Prices and availability are provider-specific and can change; the connected catalog is the source of truth.

9. Better Invitations and Group-Based Access​

Invitations now support more controlled onboarding for communities and organizations.

What changed​

  • Invite links and tokens received a rebuilt account-creation and first-login flow.
  • Invitations can carry predefined group membership where the administrator allows it.
  • Invite comments help administrators remember an invitation's purpose.
  • Delegated administrators have clearer limits and cannot invite people into the built-in administrator group.
  • Allowlist, expiration, invalid-token, and redirect behavior now produces more accurate messages.
  • SHEF-compatible invitation and account-creation handoffs are available where that service is enabled.

What you can do​

If you receive a NuQloud invitation, open it in the browser where you intend to complete setup, follow the account-creation steps, and save the Authentication File when prompted. If a link is expired or invalid, request a fresh invitation instead of repeatedly retrying it.

10. Collaboration: Talk, Cross-Cloud Files, Scrum, Calendar, and AI​

NuQloud's collaboration layer expanded in several directions. Some capabilities are generally enabled, while others depend on your provider or are early previews.

Cross-cloud file sharing in Talk​

The new NuQloud federated Talk files component is enabled by default on supported, updated installation paths. It is intended to make file sharing work more predictably in conversations that cross cloud boundaries. Actual cross-cloud behavior requires participating servers to have compatible versions and federation configuration.

The older direct Q-Chat/Talk relay has been deprecated because changes to the Q-Chat protocol made the previous mapping and relay model incompatible. NuQloud Talk itself remains fully supported for cloud chat, calls, and meetings; only the legacy Q-Chat relay is retired while a better replacement is designed.

NuQloud Scrum​

Where enabled, NuQloud Scrum turns selected Talk conversations into project workspaces:

  • a Talk conversation becomes a project;
  • a message reply chain becomes a task;
  • thread activity is mirrored into the task record;
  • shared files can be copied or linked into the project/task Files structure;
  • /todo, /doing, /done, and /blocked replies can update task status when bot commands are enabled.

Talk remains the primary conversation space. Generated Files workspaces make the project easier to review outside the chat. Deck mirroring and automatic summaries are scaffolded but are not yet complete and should not be announced as finished features.

NuQloud Master Calendar​

A NuQloud master-calendar component and setup automation were added for supported instances. It is provider-managed infrastructure intended to improve shared scheduling and calendar configuration. The visible Calendar and appointment features still depend on which apps and calendars your provider enables.

NuQloud AI​

NuQloud AI can be installed from its public application repository and registered as a shared Talk bot. Providers may restrict it to approved groups. This means an enabled instance can offer AI assistance inside selected Talk spaces without exposing it to every user by default. The exact models, limits, data policies, and availability are provider-specific; check your instance's policy before sharing sensitive material with any AI tool.

NuQloud World preview​

NuQloud World is an optional spatial interface preview. It presents available NuQloud services as an interactive world, includes keyboard/accessibility alternatives, respects reduced motion, and gracefully handles services that are not installed. It is currently a navigation and discovery preview: it does not yet publish data or perform privileged operations.

11. Managed Recovery and Safer Security Defaults​

Security work over the last six months focused on reducing dangerous defaults while making legitimate recovery and everyday use less frustrating.

What changed​

  • Users can opt into Managed Recovery for an eligible decentralized account.
  • The protected backup password is stored as an encrypted escrow record rather than plaintext.
  • Recovery requires both the user's recovery passphrase and a short-lived, one-time administrator-issued code.
  • Failed attempts trigger rate limits and temporary lockouts.
  • Recovery does not reveal or reset a local NuQloud/Nextcloud login password.
  • High-risk Q-App requests receive an extra confirmation even during an unlocked session.
  • Account and publishing unlock controls were simplified, with advanced timing controls moved out of the normal workflow.
  • Default approval periods and prompts were adjusted to reduce confusion and repeated confirmations without removing protection for spending or signing.
  • Broker routes received separate read/write rate limits, safer setup credentials, normalized OIDC scopes, more stable signing-key setup, and better secret redaction.
  • Qortal node API-key validation and routing were hardened.

Important recovery limitation​

Managed Recovery helps an already signed-in user recover an escrowed decentralized backup password. It is not a way for an administrator to read your secret at rest, and it is not a general reset for a user who has lost access to the NuQloud cloud account. Keep your own Authentication File and password backups.

12. Calls, Meetings, Notifications, and Everyday Cloud Use​

Many smaller changes improve the parts of NuQloud people use every day.

What changed​

  • Talk high-performance signaling, TURN/STUN, media, recording, proxy, and port configurations were hardened across normal and shared-host installations.
  • Talk notifications are included in the updated notification workflow.
  • Notification API changes were handled so removed upstream behavior no longer breaks setup.
  • Mail invitation templates and NuQloud-branded email presentation were improved while preserving security-sensitive links and localized message content.
  • The branded PWA install page now better reports whether the app is already installed.
  • PWA registration, favicon behavior, push/device registration, and first-load handling were repaired.
  • Desktop, mobile, and browser guides now explain which client is best for notifications, sync, uploads, chat, and calls.
  • Upload-size configuration was separated from decentralized publish-size limits, so ordinary cloud uploads and QDN publishing can be managed appropriately.
  • Default template/skeleton files are kept only when intended instead of repeatedly reappearing after upgrades.

13. Reliability Improvements You May Notice Only When Something Goes Wrong​

A large part of this release cycle went into making NuQloud instances easier to install, update, repair, and operate. These changes are mostly handled by providers and administrators, but they directly reduce downtime and broken sessions.

What changed behind the scenes​

  • Supported installations can adopt existing Nextcloud VMs and hybrid/shared-host layouts more safely.
  • Shared Qortal nodes can serve multiple NuQloud instances with validated port and API-key configuration.
  • External reverse proxies and bundled HTTPS modes now retain the correct topology through updates and restarts.
  • Domain migration tooling keeps public URLs, trusted proxies, OIDC settings, and related services aligned.
  • Installers can run in one-click mode, resume idempotently, validate required services, and preserve locally configured values.
  • Full rebuild/recreation now includes external-auth services when requested and refreshes required secrets more reliably.
  • Nextcloud major upgrades can automatically traverse required consecutive versions, creating and verifying a backup for each hop.
  • Incompatible apps can be handled during an upgrade, updated against the new core, and restored when safe.
  • Interrupted upgrades retain a journal and can resume the pinned incomplete step instead of silently changing SSL/proxy modes.
  • Missing image-owned core dependencies can be repaired without replacing user data, configuration, or custom apps.
  • Maintenance-mode upgrades skip already-settled schema work and continue with service restoration.
  • Service readiness, app compatibility, Files permissions, cron, background jobs, OIDC, Talk, Office, proxy alignment, and Qortal gateway paths have expanded diagnostics and validation.
  • Resource limits were adjusted to prevent failures during large operations.

For users, the practical result should be fewer unexplained logouts, fewer blank decentralized apps, fewer stuck publishes, more predictable upgrades, and quicker recovery when an instance restart or upgrade is interrupted.

14. New Global NuQloud Discovery Is Beginning—But Is Not Finished Yet​

The foundation for a NuQloud Federation Registry has been added. Its purpose is to help people discover participating NuQloud clouds and, eventually, explicitly published cross-cloud profiles using QDN as the durable registry layer.

The current foundation includes the directory interface, local publication settings, privacy boundaries, and an authenticated snapshot API. The trust and publication protocol is still being completed. The design separates:

  • a normal user's minimal instance pointer, which can help others discover a cloud without publishing a user directory; and
  • an authoritative instance directory, which must prove that its QDN publisher is authorized by that NuQloud instance before it can publish global instance data or an opt-in user list.

This distinction prevents an arbitrary publisher from merely claiming to be a server administrator. User-directory inclusion is intended to remain opt-in and revocable.

What you can do today: on updated instances, you may see the new registry/directory surface and honest empty or offline states. Do not rely on it as a complete global directory until your provider announces that registry publication and verification are active. No user should be listed globally merely because the foundation app is enabled.

Six-Month Change Record​

The sections above describe the practical result. This condensed record makes the full scope easier to audit.

March 14–31: publishing and service experience​

  • Repaired Talk networking, STUN/TURN, proxy ports, and no-SSL/shared-host conflicts.
  • Expanded provider package and connector management.
  • Reworked Dashboard areas and mobile behavior.
  • Fixed checkout, invoice paths, QORT sends, unconfirmed-transaction display, and qortal:// link handling.
  • Added connector-driven package synchronization and safer failure behavior.
  • Improved multi-file publishing, confirmation prompts, notifications, status indicators, unlock settings, and mobile publishing controls.
  • Improved PWA installed-state feedback and purchase-link navigation.

April: queued publishing, recovery groundwork, and hybrid deployments​

  • Added and hardened existing-Nextcloud/hybrid installation and shared-proxy tooling.
  • Added broader diagnostics, readiness checks, Qortal node configuration checks, Talk validation, and permission repair.
  • Introduced queued publishing and its viewer, wallet-unlock continuation, publish estimation, retry/edit/cleanup behavior, and richer notifications.
  • Added decentralized account recovery paths and better QDN/Q-App fallback behavior.
  • Moved the Talk embed into conversation settings.

May: encryption, safer approvals, user documentation, and provider automation​

  • Simplified unlock behavior and concentrated advanced timing settings in the advanced area.
  • Added sharing-key encryption/decryption and private file-index updates.
  • Improved Q-Manager-compatible publishing behavior and post-unlock filtering.
  • Expanded CHD/provider account, order, service, storage, connector, and automatic-account-creation tools.
  • Corrected pricing/credit formatting and name-registration amounts.
  • Added extra confirmation for spending actions while the wallet is unlocked.
  • Added the first full user-documentation set.
  • Improved Talk high-performance backend port coordination.

June: invitations and upgrade preparation​

  • Rebuilt invite-token and link-based account creation.
  • Improved first-login behavior for invited users.
  • Prepared app compatibility for newer Nextcloud versions.
  • Added hybrid Qortal rebuild support.

July: identity provider, Scrum, World, orchestration, and upgrade resilience​

  • Added safer major-version upgrade flows, validation, backups, and logging.
  • Completed the NuQloud identity-provider setup flow and operational guidance.
  • Improved rate limits, OIDC signing keys, scope normalization, secret handling, and Talk notifications.
  • Introduced NuQloud Scrum and its Talk-first workspace/task model.
  • Added the initial NuQloud World spatial interface preview.
  • Connected provider orchestration to authorized management tools.
  • Added group-aware invite links and predefined group handling.
  • Expanded shared-host, Office, signaling, recording, and Qortal node orchestration checks.

August: passwordless access, guides, PWA, recovery, AI, and unified management​

  • Introduced the passwordless-first Authentication File architecture and migration tooling.
  • Fixed preparation-mode, invited-user, and returning-browser handoffs.
  • Added account-deletion handling and stronger account/session continuity.
  • Added the Guides hub, device setup tour, progress controls, and mobile/desktop guidance.
  • Added magic-link authentication where enabled.
  • Added one-time authentication-file sharing/download flows with consistent filenames.
  • Expanded storage and package assignment for authorized operators.
  • Added NuQloud AI installation and shared Talk-bot registration with optional group restrictions.
  • Added NuQloud Master Calendar support.
  • Unified user and delegated account management.
  • Improved billing catalog, checkout email, invoices, package detail, logging redaction, and recreation reliability.

September 1–14: accounts, wallets, Dashboard V2, themes, federation, and seamless upgrades​

  • Added multiple linked Qortal accounts and backup-file-first linking.
  • Added compatible foreign-coin wallet balances, history, and sending with approval protection.
  • Improved storage, package, payment, and Decentralized Apps status handling.
  • Added the NuQloud deployment profile and rebuilt Dashboard V2.
  • Added the NuQloud Branding app, cloud-wide themes, user light/dark choice, accessibility-preserving policy controls, personal Advanced Theming, and Ocean/Orchid/Ember palettes.
  • Added SHEF-compatible sign-up and invitation handoff where enabled.
  • Hardened OIDC recreation, refresh, race, and session-restoration behavior.
  • Deprecated the incompatible legacy Q-Chat/Talk relay.
  • Added cross-cloud Talk file sharing to supported default installations.
  • Added automatic, backed-up, resumable multi-major Nextcloud upgrades and recovery for incomplete core/schema states.
  • Added the first Federation Registry discovery foundation and continued NuQloud AI/hybrid-instance improvements.

What We Recommend Every User Do Now​

  1. Open the NuQloud Dashboard and resume the setup guide.
  2. Save your NuQloud Authentication File and password in a secure location outside the cloud.
  3. Review linked decentralized accounts and create a current backup for each important account.
  4. Check Appearance and accessibility and choose the mode and approved palette that work best for you.
  5. Review Decentralized App approval settings and keep high-risk confirmations enabled.
  6. Before publishing, confirm whether the destination is ordinary cloud sharing, private QDN publishing, or public QDN publishing.
  7. If you use multiple devices, install the PWA and the appropriate Files/Talk clients described in the Guides hub.
  8. Ask your provider which optional features—NuQloud AI, Scrum, World, managed recovery, cross-cloud federation, supported foreign coins, and add-on packages—are active on your instance.

Looking Ahead​

The last six months were about making NuQloud more usable as a daily cloud while preserving the decentralized capabilities that make it different. The next steps are to finish verified, privacy-respecting federation discovery; continue improving cross-cloud collaboration; complete planned Scrum mirrors and summaries; and keep simplifying the experience without weakening user control.

Thank you to everyone testing NuQloud, reporting confusing behavior, and helping shape a cloud that connects familiar collaboration tools with decentralized identity, publishing, and applications.