Documentation
Operate Nariqui with confidence.
Set up your writing workspace, bring in existing projects and keep a recoverable copy of your work.
Getting started
Install Nariqui using Docker Compose or Portainer for self-hosting, or choose Windows or Linux Desktop for a straightforward setup on your PC. Self-hosting pulls the official image automatically. Offline archives and signature verification are optional.
Projects and import
Editable native projects live in operator-configured project locations. Portable lowercase .qui packages are used for transport, backup and restore. Supported legacy Manuskript .msk sources are inspected read-only and imported into a separate native project.
Operation and recovery
See Advanced setup for custom project folders, backups and recovery, and authenticated remote access. Keep backup copies separate from your working projects.
Compatibility
Use a current desktop version of Chrome, Firefox or Microsoft Edge. The macOS host setup, Safari and iOS have not been fully tested for this Beta.
Frequently asked questions
Practical answers for Windows Desktop and the self-hosted Beta.
Which version of Nariqui should I choose?
Choose Windows Desktop or Linux Desktop for straightforward installation and writing on one PC. Choose self-hosting if you prefer running Nariqui on your own server or NAS and accessing it from multiple authorized devices. Releases may include different features; check the version and compatibility notes before transferring work.
What is the difference between Docker Compose and Portainer?
Both install the same self-hosted Nariqui application. Docker Compose uses configuration files and terminal commands; Portainer provides a graphical interface for managing Docker containers. Paste the official YAML and deploy: both methods pull ghcr.io/aurelica/nariqui:latest automatically. No image import or command-line signature verification is needed for ordinary installation.
Do I need Docker for the Windows edition?
No. Windows Desktop includes its application runtime. Its conventional Windows installer does not require Docker, Python, Node or WSL. Get the Windows Beta from the official download page.
Do I need an internet connection to write?
Nariqui is designed for local writing. Windows and Linux Desktop run on your PC; self-hosted Nariqui needs a connection to the machine hosting it, whether on your own computer, local network or a secured remote connection. Optional external services, such as a configured AI provider, may need internet. Final Windows offline validation is pending.
Where are my manuscripts stored?
Windows Desktop stores working projects on your Windows machine by default, within its configured writing location. Linux Desktop defaults to your Ubuntu user’s local Nariqui data folder. Self-hosted Nariqui stores them on the Docker host’s configured storage. A browser interface does not mean your manuscript is stored in a cloud service. Review the destination shown when creating or importing a project; arbitrary Windows folder selection is not currently offered.
Can I access my projects from another computer?
The self-hosted edition can serve authorized devices through a properly secured network configuration, such as a VPN and authenticated HTTPS access. For containerised Nginx Proxy Manager on the same Docker host, use the documented existing-network profile with no published application port, HTTPS and a password Access List. The operator must configure this access; Nariqui does not supply user authentication automatically. Windows Desktop is currently intended for local use on its own PC.
Can I store my Windows projects on a NAS?
A NAS can hold independent backups and exported .qui packages. Keep active Windows working projects on reliable local storage: directly editing them over a network share is not a generally supported Beta guarantee. Network filesystems vary in how safely they lock and preserve an open project.
Can I transfer projects between desktop and self-hosted Nariqui?
Use supported .qui backup/export and import/restore workflows, subject to compatible project and application versions. Check both releases’ compatibility notes before transferring work. Moving an exported project is explicit portability, not live or automatic synchronization.
How do I back up my writing?
Use Nariqui’s supported project backup/export features and keep independent copies. Self-hosted operators should also follow the documented volume backup, verification and recovery procedures. One exported file or a network share alone is not a complete backup strategy; verify that you can restore your copies.
Does Nariqui update automatically?
Not currently. The latest image tag follows approved releases, but running containers change only when you deliberately pull and redeploy. Keep automatic container updaters off and back up first. You can pin a version or published image digest for reproducibility. For Windows Desktop, save and close your projects, then quit Nariqui before running an approved update installer.
Which browsers and operating systems are supported?
Use a recent desktop Chrome, Firefox or Microsoft Edge. Windows Desktop targets Windows 11 x64; the existing self-hosted Beta supplies a Linux/amd64 Docker image for a compatible Docker host. The macOS host setup, Safari and iOS have not been fully validated. Linux Desktop supplies an x86_64 .deb for Ubuntu 22.04, 24.04 and 26.04 LTS with the native GTK 3 launcher. Automated graphical checks use Xvfb/Openbox; physical Ubuntu 22.04 launcher appearance/status/Quit are owner-verified, not complete GNOME/Wayland acceptance. There are no native macOS or ARM installers and no native ARM container image.
Is Nariqui free, and do I need an account?
The current proprietary v0.3.0-Beta is free and permits indefinite use of the installed version under its included licence. This does not promise future versions or services will have the same terms. Ordinary Windows Desktop, Linux Desktop and self-hosted use do not require a mandatory Nariqui cloud account; optional external providers may require their own account. Read the terms supplied with each approved release.
Can I recover writing after accidentally closing a browser tab?
Windows Desktop, Linux Desktop and the matching self-hosted Beta can reopen the latest draft confirmed as Retained, using the same browser profile and local address with intact storage. Retained is separate from Save: pending or failed retention is not protected, and deleted or damaged browser data cannot be guaranteed recoverable. If retention fails, keep the tab open and Save.
Do not assume older releases include this recovery. Keep using Save and independent backups, and check your release’s recovery instructions.
Is my writing private?
Your projects stay on your Windows or Ubuntu PC, or self-hosted infrastructure unless you deliberately use an external service or share them. Optional AI lookups go to your configured provider; problem reports contain only what you choose to send. Website statistics are separate from your manuscripts. Local storage is not a promise of absolute privacy or security: protect access to your computer, server and backups.

