What is Rail? Capturing notes, tasks and decisions without leaving your Windows workflow

Rail is a Windows edge workspace designed to capture a note, task or decision without pulling you away from the work already on your screen.

Imagine an idea appears while you are writing a product roadmap, a follow-up task comes out of a meeting, or you make a decision you need to remember later. The usual flow is to leave the current application, open another tool, find the right place, record the item and then return. Rail is designed around reducing that distance.

Open Rail or read the Rail product and systems case study.

What is Rail?

Rail is a fast-capture workspace designed for Windows. It stays available at the edge of the screen and can be opened through a global shortcut. The goal is to record a thought close to the context where it appeared instead of moving into another heavy workspace just to save it.

Rail does more than store notes. The same capture surface separates three core content types:

• Note
• Task
• Decision

That distinction matters because an idea and an action are not the same thing. Rail tries to make the meaning of the captured item explicit at the moment it is recorded.

What does Rail do?

The current product scope brings these use cases together:

• Capture a quick note while working or during a meeting.
• Turn something you remember into a task and keep track of it.
• Store product, project or everyday decisions as their own content type.
• Organize notes and tasks with folders.
• Write with Markdown or Rich Text.
• Separate task priorities through an Eisenhower view.
• Reach Rail from the application you are using through global shortcuts.
• Use the local workspace on the device.

Rail is not intended to grow into an everything-dashboard. Its product boundary is keeping the distance between a thought appearing and that thought being safely recorded as small as practical.

Why use Rail?

Rail does not make an unmeasured performance claim such as "you will work faster." The product decision is more concrete: reduce how many contexts you have to cross just to record something.

A normal capture flow can look like this:

1. Leave the current work. 2. Open the note or task application. 3. Find the right destination. 4. Write and save. 5. Return to the original work.

Rail tries to compress that flow into an edge capture surface. Write the thought, classify it and close the panel.

That makes Rail relevant to Windows users who repeatedly capture small pieces of information during the day. Developer, designer, product worker, researcher, student or office worker are secondary labels. The shared problem is not wanting to abandon the main task when the thought "I need to remember this" appears.

How does Rail work?

1. Capture

Open Rail from the edge of the screen or through the global shortcut and write the thought.

2. Structure

Choose whether the input is a note, task or decision. Place it into the relevant folder or work context when needed.

3. Continue

Close Rail after the capture and return to the application you were already using.

Those three steps summarize the product model: capture, structure, continue.

How is Rail different from a conventional notes app?

Calling Rail only a "Windows notes app" misses part of the product. Notes are one layer, while three product decisions shape the experience:

• Location: Rail uses the edge of the screen instead of making a main dashboard the first interaction.
• Content type: Notes, tasks and decisions share the same capture surface while remaining distinct.
• Continuity: Local use is the base layer; Cloud Sync is enabled with Rail Pro.

Folders, Markdown/Rich Text, tasks and the Eisenhower view sit around that core capture flow as organization tools.

What is the difference between Rail Pro and Lifetime?

Rail's commercial model keeps two kinds of value separate.

Rail Pro

• Monthly or annual subscription.
• 7-day trial.
• All local Rail features.
• Cloud Sync.
• Cross-device continuity.
• Future Rail updates.

Lifetime Local

• One-time local licence.
• All local Rail features.
• No Cloud Sync.

This separation is deliberate. Lifetime is not positioned as a cheaper copy of the subscription. The recurring value of the subscription is Cloud Sync and continuity across devices. Because prices can change, the source of truth for current pricing is Rail's own pricing surface.

What is Rail's current status?

As of August 31, 2026, Rail's web sales surface, interactive Windows demo, pricing system and Paddle plan configuration are in place. The Windows product itself is explicitly kept in pre-release state and is actively developed.

That distinction matters. A pre-release product should not be presented as generally released. For the same reason, this page does not invent public user counts, ratings, revenue or performance metrics. The evidence available today is the working product surface, demo, product scope and commercial-model decisions.

For the technical side, continue to the Rail case study.

Quick answers

Is Rail a notes app?

Partly. Rail captures notes, but its product model combines notes, tasks and decisions in the same fast-capture surface.

Which operating system is Rail for?

Rail is designed for Windows.

Can Rail be used locally?

Yes. Rail's local features work on the device. Cloud Sync is enabled separately with Rail Pro.

Does the Lifetime licence include Cloud Sync?

No. Lifetime is positioned as a local licence. Cloud Sync is part of the Rail Pro subscription.

Can I try Rail before buying?

Rail has an interactive Windows demo on the web that requires no account. Rail Pro is also offered with a 7-day trial.