AMAZON EFS. WINDOWS ACCESS. ROADRUNNER SMB.

Windows storage on AWS.
Built for the login storm.

Connect FSLogix profiles and Windows file shares to Amazon EFS through one SMB platform. Keep Active Directory integration and your files in your own AWS account.

Runs in your AWS account. Your files stay in EFS.
Technical overview + demo Rick Braddy · Founder, Roadrunner SMB
Roadrunner mascot with orange goggles and an FSLogix backpack running through cloud file infrastructure.
ROADRUNNER SMBCloud storage. Windows access.
SMB3Windows file access
Amazon EFSFiles in your AWS account
2–8Supported production nodes
AVAILABLE THROUGHAWS Marketplace
Fits your existing environmentAmazon EFSSMB3Active DirectoryFSLogixAWS Marketplace

A CLOSER LOOK AT ROADRUNNER

See what connects
your Windows workloads.

Explore the architecture and the administration tasks behind an EFS-backed Windows file service.

Original Roadrunner diagram showing Windows FSLogix clients, metadata caching, DynamoDB and the Amazon EFS file-data path.
Original product architecture graphic. Diagram labels are in English.

Windows accessSMB3 for Windows clients and FSLogix profiles.

Separate pathsMetadata handling and file-data I/O have different jobs.

Your AWS accountPersistent files remain in Amazon EFS.

PRODUCT WORKFLOW

A working file service.
A clear administrative workflow.

Explore the documented product functions. This interactive overview describes the workflow; it is not a screenshot of the Admin UI.

Read the Admin Guide (English)

SHARE ADMINISTRATION

Create and manage
Windows file shares.

Manage SMB shares through the product's browser-based Admin UI, with access based on your Active Directory environment.

  • Share configuration
  • Windows client access
  • Active Directory users and groups

EXPLORE THE PLANNING MODEL

More serving nodes.
One shared dataset.

Compare published planning configurations and see how instance size and node count affect the model.

Model-based planning guidance, not a production guarantee. Validate your own FSLogix workload. The explorer covers 4, 6 and 8 nodes.

Read the source and sizing assumptions (English)
02 / CAPACITY EXPLORERFSLogix workload model
40,000Modeled concurrent users
40Modeled logins / second
080,000

STORAGE THAT STAYS TOGETHER

Grow the file estate.
Keep a common foundation.

Explore the difference between adding storage islands and scaling an SMB layer over a shared EFS dataset.

Original architecture comparison: separate provisioned file-server islands versus one EFS dataset with independently scaled SMB nodes.
Illustrative product architecture comparison, with English labels. Software and AWS usage charges apply; see pricing.
Understand the full cost model

TECHNICAL OVERVIEW + DEMO

Inside the Roadrunner SMB 1.3 demonstration.

Follow the metadata and file-data paths, then review the setup used to demonstrate concentrated FSLogix login demand.

Download the technical overview (PDF, English)
Cover of the technical overview and demo presentation.
English presentation. Architecture illustrations, not product screenshots.

Demo nodes

2 × c6i.2xlarge

LoginSim input

50 new logins launched every 5 seconds.

Admin visibility

Dashboard and metrics: sessions, throughput, latency, CPU, RAM and cluster health.

Visible demonstration, not a maximum-capacity benchmark. Launched logins describe test input, not measured completed-login throughput.

THE WORKLOADS

Two storage challenges.
One common foundation.

Desktop sessions and long-lived business files create different demands. Give both a deliberate storage architecture.

01

DESKTOP PROFILES

Plan for the morning
everyone signs in.

FSLogix login and reconnect events concentrate storage activity into short windows. Evaluate the profile workload your users actually create.

Explore desktop workloads
02

BUSINESS FILE SHARES

Let the file estate grow
with the business.

Home directories and departmental files need familiar Windows access. Keep persistent files in EFS while planning SMB serving capacity separately.

Explore shared file storage

THE PLATFORM

Built around
your infrastructure.

A focused file-services platform for teams making deliberate choices about Windows storage on AWS.

Inside the architecture
01 / ACCESS

Windows-native access

SMB3 and Active Directory connect Windows users and applications to the file layer.

02 / OWNERSHIP

Files in your account

Persistent file data stays in your Amazon EFS environment, without a proprietary file format.

03 / GROWTH

Separate serving from storage

Assess serving capacity and storage growth as separate architectural decisions.

Rick Braddy, founder of Roadrunner SMB.
Rick Braddy · Founder, Roadrunner SMB

THE PERSON BEHIND ROADRUNNER

Built by Rick Braddy.

Rick Braddy founded Roadrunner SMB. His background includes leading technology for Citrix’s XenApp and XenDesktop group as CTO, and founding SoftNAS, where he was CEO.

That experience in virtual desktops and cloud file storage informs Roadrunner’s focus on Windows workloads on AWS.

Former CTO, Citrix XenApp & XenDesktop groupFounder & former CEO, SoftNAS
Meet the founder
Original Roadrunner architecture whitepaper cover with file services connected to cloud storage.

TAKE THE DETAIL WITH YOU

The engineering.
The architecture.
The next decision.

Read the architecture whitepaper and bring concrete questions to your evaluation. Understand identity, deployment topology and the file-data path before deciding.

PDF in English. Original cover artwork from the Roadrunner website.

BEFORE YOU START

A few things
worth knowing.

Ask a technical question
Where does the product run?

Roadrunner SMB is deployed into your AWS account. The public website is separate from the software you deploy.

Does the Eval Kit have usage charges?

Yes. AWS infrastructure and applicable software usage charges apply. The Eval Kit is for evaluation and automatically uninstalls after 30 days.

Are capacity figures performance guarantees?

No. Published capacity models are planning guidance. Define success criteria and validate the actual workload before making a production decision.

Where should we begin?

Start with your desktop environment, storage requirements and deployment constraints. Review the architecture or send a business inquiry to discuss a suitable evaluation.

YOUR NEXT STEP

Let's talk about
your AWS environment.

Bring your use case, questions and deployment requirements. Start a focused technical conversation.

Start a conversation