Browser-shaped workspace with the cabinet one click away
The desktop shell keeps browsing, language switching, search sources, and the workspace cabinet together in one clear interface.
An open-source desktop-first workspace for browsing, writing, editing, files, notes, projects, tools, and publishing preparation.
The preview now includes Linux, Windows, and macOS builds generated with GitHub Actions. Linux .deb is the recommended Linux installer.
Browser-shaped research, workspace cabinet modules, editor flow, notes, files, tools, catalog, and desktop installers in one early preview.
IRGEZTNE is designed around active work: files, notes, projects, writing, and the browser-shaped shell that connects them.
Instead of scattering work across disconnected services, IRGEZTNE is shaped as a calmer local-first environment where the user owns the workflow.
Larger real screens from IRGEZTNE Workspace v1.0.0-preview.2: browser shell, workspace cabinet, editor, tools, notes, and catalog.
The desktop shell keeps browsing, language switching, search sources, and the workspace cabinet together in one clear interface.
Drafts, templates, preview, and writing tools stay inside the workspace.
Recent files, projects, notes, and main routes are visible from one cabinet.
Translation, comparison, and extraction tools are prepared as working utilities.
Current templates and planned catalog items are shown honestly inside the product.

Notes and workspace context stay close to browser research, files, and editing.
IRGEZTNE v1 is focused on a strong working core first.
Library of files, materials, and working sources.
Quick notes, fragments, ideas, and references.
Top-level containers for structured work.
Writing, editing, preview, and publishing flow.
Active space for current tasks and recent items.
Supporting tools inside the environment.
Early desktop preview builds are available from GitHub Releases for Linux, Windows, and macOS.
Early preview builds are not code-signed yet. Platform buttons below download the release files from GitHub Releases. Linux users should start with the .deb installer. AppImage is included as experimental.
IRGEZTNE Workspace v1 Preview focuses on the working core first. Future modules stay visible as direction, not as finished promises.
These modules already exist in the workspace and form the current working core.
These modules are planned for later versions and should be treated as in development.
Use these links for contact, source code, preview package status, feedback, and bug reports.
The first public package now includes simple legal/contact pages. Contact and download links are prepared for the public preview.
Explains local-first data, optional analytics, no cookies, and no sale of personal data.
Use this slot for product usage terms, desktop build notes, and future distribution rules.
Keep one clean route for help, support, bug reports, or product questions.
This section is intentionally longer now, so the product face explains the desktop-first idea better before someone downloads it.
Not exactly. It includes browsing, but it is built as a local-first workspace where files, notes, projects, and editor flow sit together.
The core idea is active work: files, drafts, previews, and modules in one shell. Desktop is the strongest place to build that first.
No. Optional network-related directions are not required for the main workflow.
No. The core model is local-first, and the product direction is to avoid forced cloud dependence.
Yes, that is part of the point. The local-first direction is meant to keep the core working even when the network is not the center of the workflow.
Yes. The main goal is to make the editor, previews, and starter site flow stronger so people can move from blank page to usable output faster.
Possibly, yes. Desktop comes first. A lighter web or mobile-facing layer may come later as a simpler entry point.
They can sit as standard footer pages such as Privacy Policy, Terms of Use, and Support. The structure is already prepared below.
Next step: replace part of the mock area with real application screenshots and link these answers to docs later.