↗FED·SHELL
Open builder ↗

UNIVERSAL URL WRAPPER / FED-OS

One URL.
Every surface.

FED-Shell is the cleanest route from a live website to a launch-ready native presence—without rebuilding the web you already made.

ANDROIDIOSDESKTOPWEB
Open the launch console →
URL IN ✦ NATIVE OUT ✦ ANDROID ✦ IOS ✦ WINDOWS ✦ MACOS ✦ LINUX ✦ PWA ✦ URL IN ✦ NATIVE OUT ✦

01 / THE PIPELINE

One input.
Many exits.

Point FED-Shell at your public HTTPS URL. The same web experience becomes the source for your mobile, desktop, and installable web targets.

NO BACKEND REQUIRED
01

Point

Bring one live URL. Keep your existing site, content, and release flow.

02

Wrap

Use Capacitor and Electron shells tuned for the platforms you select.

03

Ship

Download clean configuration files and run the build in your own repo.

02 / SURFACES

Meet your users
where they are.

Native chrome where it matters. A fast installable web surface everywhere else.

FED-OS READY
◆

Android + iOS

Capacitor-powered mobile shells with a simple sync workflow.

⊞

Windows + macOS

Electron targets for desktop distribution and local workflows.

◎

Linux

Keep the same URL and ship a first-class desktop surface.

↗

Web / PWA

Installable metadata and display modes generated in seconds.

03 / DEPLOYMENT

Plain HTML stays plain.

CLOUDFLARE WORKERS BUILDSnpx wrangler deploy --assets=.
Launch builder ↗

For a plain HTML repo: leave the build command blank, deploy the root assets, keep production on main, and let the URL remain the source of truth.

THE OPERATING MODEL

Not a demo.
A repeatable route.

FED-Shell exists to make the path from an already-working website to a platform-ready app clear enough to repeat across projects.

01 / 04
01

Keep the source stable

Your public HTTPS website remains the source of truth. You can deploy content and app packaging on separate rhythms.

02

Choose the shell

Capacitor brings the URL into mobile-native projects. Electron gives the same URL a desktop window and distribution path.

03

Generate the handoff

Use the launch console to create explicit JSON configuration instead of manually copying values across several platform projects.

04

Own the release

Build and sign from your own repository and credentials. FED-Shell stays a transparent wrapper, not a black-box hosting service.

WHERE IT FITS

Six surfaces.
One source.

Choose the destination based on how your audience works, not because every project needs every installer.

02 / 04
SurfaceUse it whenTypical output
AndroidYou need Play Store reach or field-device distributionCapacitor + Gradle
iOSYou need TestFlight, App Store, or managed Apple devicesCapacitor + Xcode
Windows / macOS / LinuxYour users expect a desktop window, menu, or installerElectron targets
Web / PWAYou want installability without a store reviewmanifest.json
DEPLOYMENT PLAYBOOK

Plain repo.
Clear command.

For a static website connected to Cloudflare Workers Builds, the standard setup is deliberately small.

03 / 04
STANDARD STATIC SETUP
Build command:  [blank]
Deploy command: npx wrangler deploy --assets=.
Root directory: /
Production:     main
BEFORE YOU DEPLOY
  • index.html is in the assets root
  • relative paths work from production
  • the deploy folder matches the command
  • no unnecessary framework build is configured
KEEP BUILDING

Need the next
level of detail?

Open the launch console for interactive configuration, or read the field guide for the full repo and release checklist.

Launch console →Read field guide ↗