Static site deployment

Push.
Done.

Deploy any static directory to the web in seconds. No config files, no dashboards, no cloud accounts to wrangle. Just your terminal and one command.

$ npm install -g fyra

How it works
01

Install the CLI

One install, globally. Run npm i -g fyra and you're ready on Mac, Linux, or Windows.

02

Create your app

Inside your project, run fyra create. Pick a name or get one assigned. A .deploy.yaml is saved locally.

03

Push it live

Run fyra push. Your directory is compressed, uploaded, and served — CDN included.


See it happen
bash — ~/my-site
$ fyra create --appname my-portfolio
App created: my-portfolio
Saved .deploy.yaml — you're good to push.
$ fyra push
Scanning my-portfolio...
Packing 38 files (1.2 MB)
Uploading... 1.2 MB sent
Deploying on server...
Done: http://my-portfolio.fyra.sh
$

"

I used to spend an hour setting up S3 buckets, CloudFront, and Route53 every time I needed to ship a landing page. Now I type fyra push and get a coffee.

Mara Lindqvist — Frontend developer

Commands
fyra register

Create a new account with your email and a password. Runs once.

fyra login

Sign in. Your session token is saved locally so you stay logged in.

fyra create

Create a new app in the current directory. Saves a .deploy.yaml with your app slug so future pushes know where to go.

--appname <name> Set a specific slug. Must be globally unique.
fyra push

Compress and upload the current directory. Your site is live the moment it finishes. Shows upload progress as it goes.

--appname <name> Push to a specific app, overrides .deploy.yaml.
fyra list

List all your apps with their live URLs and deployment status.

fyra set-domain

Attach a custom domain to your app. CDN is activated and DNS configured automatically.

--appname <name> The app to attach the domain to.
--domain <domain> Your hostname, e.g. portfolio.com.
fyra whoami

Print the email of the currently logged-in account.

fyra logout

Clear the local session. You'll need to login again to push.


Our iron.
Our network.
Your speed.

We don't run on AWS, GCP, or Azure. Fyra operates its own physical infrastructure and holds its own Autonomous System Number (ASN) — meaning your traffic travels on our network, peered directly with the internet, not routed through a hyperscaler's cloud.

Every site is served from the point of presence closest to your visitor, with no cold-start latency, no shared noisy neighbours, and no per-request fees passed on to you.

Fyra Network — ASXXXXX
Singapore
Southeast Asia
Tokyo
Northeast Asia
Frankfurt
Central Europe
New York
US East
Los Angeles
US West
More coming soon
Sydney · London · São Paulo