Local-first workspace
Projects, source material and core content work are centered in the Windows application and its local data.
- Organize projects and source material
- Create and review content locally
- Connected features have additional requirements
Security approach
AvenRail is built around a local Windows workspace, with distinct boundaries for account access, AI assistance and supported publishing services.
Windows-first · In development
Trail at NorthstarImage · Project source
Summit viewImage · Project sourceYour source material, organized in one project.
Product concept · Sample data
Keep the work close. Understand the connection before you use it.
Projects, source material and core content work are centered in the Windows application and its local data.
Account access, AI requests and publishing connections have distinct purposes and authorization steps.
Keep the selected version, destination and preparation stages in view when a supported workflow uses them.
Connected data boundaries
Your workspace stays central. Connected features use their own defined boundaries.
Explore an example. These are separate workflows, not one required pipeline.


Trail notes, photography and a place for your next idea.
Draft · Sample contentCore project work is local-first. Connected features have their own requirements.

Turn trail notes and source material into a story you can refine.
Your local workspace Local content work remains centered in the Windows application. Compatible local inference depends on a supported runtime, hardware and qualified model; it does not make every connected feature available offline.
Conceptual explanation, not live monitoring or a deployment diagram. Optional Cloud Sync is a separate, activation-dependent capability; local-first does not mean information can never leave your device.
Core project data belongs to the desktop workspace. Local-first is not a promise that every feature works offline.
Account Web has its own verified session. Platform connections follow their own supported sign-in and workflow boundaries.
A selected draft for AI and content prepared for publishing are different requests. Review the relevant workflow and privacy information.
Choose an appropriate workflow, understand when external services may be involved, and review the result before using it.
Built-in Cloud assistance can process selected content through an external service when you invoke an eligible workflow.
The intended on-device option depends on supported hardware, runtime and model qualification.
Prepare a trusted prompt, use a separate AI product, then paste its result back for validation and review.
Account access
The desktop and system-browser account sessions are independent. Opening Account Web does not transfer your desktop session or expose local project files.
Northstar field journalProject materialSource, images and draftsDesktop sessionPublishing-platform accounts use their own supported authentication paths. An AvenRail account is not a replacement for those accounts.
Publishing review
Review the selected content and destination. Supported APIs and assisted browser paths have their own preparation, approval and execution steps.
Meet NorthstarProfessional postPublished
The trail behind the ideaConversational postPlanned
Your next chapter starts outsideShort announcement · Selected exampleDraft
A field journal, thoughtfully madeEmail storyPlannedSelected example is a draft. Preparation is not publication.
Task status does not prove external engagement. Available results depend on the platform and connected service.
Explore publishing workflowsCheck the mode and where selected information may be processed.
Preparation, approval and execution depend on the supported path.
Accounts, eligibility and platform support differ by feature.
Your core project content is centered in the Windows workspace. Selected information can leave the device through connected workflows. Optional Cloud Sync has its own scope and activation requirements; local-first does not mean completely offline.
When an eligible connected workflow requires it, such as a supported Cloud AI request. The information involved depends on the feature. Cloud availability, authorization and applicable credits remain separate requirements.
Account Web verifies its browser session independently from the desktop. Publishing-platform accounts and browser-assisted workflows have their own supported authentication boundaries. Website account access does not automatically expose local projects.
Supported workflows show content, destinations and preparation or review stages where applicable. Check the selected path: direct API and assisted-browser execution differ, and a planned date is not proof of publication.
Read the existing privacy information for this website. This product overview is not a security certification or a substitute for applicable privacy information.
Clearer choices, connected work
A preview of the intended Windows-first experience, still in development.