Security approach

Your content starts locally.Connected features stay clear.

AvenRail is built around a local Windows workspace, with distinct boundaries for account access, AI assistance and supported publishing services.

Windows-first · In development

Your content workspace
Northstar / AssetsSample project

Project material

3 sample items
Trail at NorthstarImage · Project source
Summit viewImage · Project source
NorthstarProduct brief
Launch brief.pdfDocument · Project source

Your source material, organized in one project.

Product concept · Sample data

What this means in practice

Keep the work close. Understand the connection before you use it.

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

Connected features, clear boundaries

Account access, AI requests and publishing connections have distinct purposes and authorization steps.

  • Account identity is separate from content
  • Different workflows use different information
  • Availability depends on the supported feature

Visible review steps

Keep the selected version, destination and preparation stages in view when a supported workflow uses them.

  • Inspect and refine authored content
  • Check the destination and workflow
  • Distinguish preparation from publication

Connected data boundaries

Understand what connects.

Your workspace stays central. Connected features use their own defined boundaries.

One workspace. Distinct boundaries.

Explore an example. These are separate workflows, not one required pipeline.

01 / Your Windows workspace

Your work starts here.

Your content workspace
Northstar / WorkspaceSample project
Northstar launch briefSource material · Local project
Content draftA field journal for everyday discoveries

Trail notes, photography and a place for your next idea.

Draft · Sample content
Projects · Source · Media · Drafts

Core project work is local-first. Connected features have their own requirements.

04 / Review & visibility

Bring the next step into view.

Your content workspace
Northstar / ReviewSample project
Draft · Sample contentA field journal for everyday discoveries

Turn trail notes and source material into a story you can refine.

Selected exampleReview a local draft
Content
Draft and review
Publishing
Task status, separate from content
Results
Where the platform provides them

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.

Local content work

Core project data belongs to the desktop workspace. Local-first is not a promise that every feature works offline.

Separate browser identity

Account Web has its own verified session. Platform connections follow their own supported sign-in and workflow boundaries.

Feature-specific information

A selected draft for AI and content prepared for publishing are different requests. Review the relevant workflow and privacy information.

AI assistance,with clear boundaries.

Choose an appropriate workflow, understand when external services may be involved, and review the result before using it.

Cloud

Selected material can leave the device.

Built-in Cloud assistance can process selected content through an external service when you invoke an eligible workflow.

  • Provider availability and eligibility apply
  • Applicable credits are required
  • Review the returned candidate
Compatible Local models Conditional

On-device processing, where supported.

The intended on-device option depends on supported hardware, runtime and model qualification.

  • Compatibility is not universal
  • Model setup can have its own requirements
  • Other connected features may still need a service
External Hybrid

A prompt out. A result back for review.

Prepare a trusted prompt, use a separate AI product, then paste its result back for validation and review.

  • You choose the external product
  • Its access, costs and data practices are separate
  • Not automatic Cloud/Local switching

Account access

Separate sign-in
and account management.

The desktop and system-browser account sessions are independent. Opening Account Web does not transfer your desktop session or expose local project files.

Publishing-platform accounts use their own supported authentication paths. An AvenRail account is not a replacement for those accounts.

Publishing review

Know what you’re
preparing to publish.

Review the selected content and destination. Supported APIs and assisted browser paths have their own preparation, approval and execution steps.

Your content workspace
Northstar / Publishing reviewSample project
Content queue4 sample pieces
Meet NorthstarProfessional postPublished
The trail behind the ideaConversational postPlanned
Your next chapter starts outsideShort announcement · Selected exampleDraft
A field journal, thoughtfully madeEmail storyPlanned
Preparation exampleYour next chapter starts outsideContent: Draft
Review content Check destination Supported path

Selected example is a draft. Preparation is not publication.

Product concept · Sample data

Task status does not prove external engagement. Available results depend on the platform and connected service.

Explore publishing workflows

Understand the AI workflow

Check the mode and where selected information may be processed.

Review content and destinations

Preparation, approval and execution depend on the supported path.

Recognize connected requirements

Accounts, eligibility and platform support differ by feature.

A few things to know

Does AvenRail keep all my content on my device?

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 does AvenRail use a Cloud service?

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.

How are my account and publishing connections separated?

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.

Can I review content before publishing?

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.

Where can I read about website privacy?

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

Explore the workspace behind these boundaries.

A preview of the intended Windows-first experience, still in development.

Explore the features