One binary runs the whole stack.

Nextweb brings its own web server, runtimes, and database. You install an application by name and deploy it with four commands.

Start the first lesson Download

curl -fsSL https://get.nextwebjs.com | bash

Linux x64. About 120 MB, free to try. On first start it asks for an email address to issue your license.

~/nextweb-tour

$ curl -fsSL https://get.nextwebjs.com | bash
$ ./nextweb
...
nextweb:/> pkg install wordpress
...
Installation order: php8.3.9-linux-x64 → mariadb-11.4.5-linux-x64 → wordpress
...
wordpress 7.1.3 installed successfully
nextweb:/> deploy company-site to www.example.com using wordpress
Site "company-site" registered for www.example.com (template: wordpress).
...
nextweb:/> commit "Deploy company website"
Committed: Deploy company website
Configuration validated.
Configuration written.
nextweb:/> apply -y
...
Site: company-site (www.example.com)
  Allocated site listen port 4001 for company-site
  Provisioning database for site company-site...
  MariaDB running (socket /tmp/nw-maria-4b18b6219aa4.sock)
  Database wp_company_site and user wp_companysite ready
  Starting PHP runtime for site...
  php-cgi listening on 19100 (2 processes, opcache off)
...
Visit: http://127.0.1.10:4001/
...
nextweb:/> verify company-site
...
HTTP check passed (200)
Response contains WordPress markers
...
All checks passed.
nextweb:/>

From a run of the first lesson. Each ... marks lines we cut.

Deploy

Four commands. Nothing starts until you apply.

01 deploy
Names the site, sets its domain, and copies in a WordPress of its own.
02 commit
Checks the change and saves it to the configuration, with a note about what changed.
03 apply
Switches it on. Picks a port, starts MariaDB and PHP, and hands the site to the web server.
04 verify
Checks the files, the database settings, and the web server, then asks the site for a page.

How a deploy works

One folder

Everything it installs stays in one folder.

PHP, MariaDB, the configuration, and every site live inside the folder you run Nextweb from. Each site gets its own copy of the application, its own database, its own PHP, and its own port.

nextweb-tour/

nextweb                          the program
nextweb_server/
  config/nextweb-services.json   the saved configuration
  runtime/                       PHP and MariaDB, installed once
  sites/company-site/
    wordpress/                   the site's own copy of WordPress
    .nextweb/state.json          what Nextweb knows about the site

Where it's going

We want Nextweb to be where web software gets published.

You write an application, build it into one package, and the machines you choose install it by name.

Works today

Running applications. On Linux x64, WordPress installs by name and deploys with the four commands above.

Works today

Packaging your own applications. You describe one in a small file, build it into a package, publish it, and install it by name. The second lesson does it start to finish. The package is encrypted; package DRM explains who can open it.

The full roadmap

When you get stuck

Nextweb is in beta. If your screen doesn't match the lesson or something breaks, open an issue on GitHub, ask in Discord, or write to support@nextwebjs.com. All three reach the person who builds it. Read a note from Bryan.

Start the first lesson Get help