beam.com 0.1.0-rc.1

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,97 @@
+BEAM.com
+Copyright 2026 Sơn Trần-Nguyễn
+
+This product is licensed under the Apache License, Version 2.0 (see
+LICENSE).
+
+The file beam.com contains the software below, and each program that
+beam.com makes contains a part of it. The file keeps these notices and the license texts in its
+zip, in the directory licenses/ ("unzip -l beam.com licenses/*" lists
+them). The source of this repository keeps the texts in licenses/.
+
+Erlang/OTP 29.1.1 (ERTS and the OTP applications in the zip)
+  Copyright Ericsson AB and the contributors of Erlang/OTP.
+  Apache License 2.0 (LICENSE). ERTS also contains code of other
+  projects (for example zlib, PCRE2, Zstandard, AsmJit and Ryu) under
+  the licenses that the headers of the OTP source files name. The zip
+  has the license texts of the LICENSES directory of OTP in
+  licenses/otp/.
+  https://github.com/erlang/otp
+
+Elixir 1.20.4 (the elixir, eex, ex_unit, iex, logger and mix
+applications)
+  Copyright The Elixir Team.
+  Apache License 2.0 (LICENSE), and the license texts of its source in
+  licenses/elixir/.
+  https://github.com/elixir-lang/elixir
+
+Cosmopolitan Libc 4.0.2 (the C runtime of the APE file)
+  Copyright 2020 Justine Alexandra Roberts Tunney.
+  ISC License (licenses/cosmopolitan.txt). Cosmopolitan also links code
+  of other projects (for example musl, FreeBSD and zlib). Its linker puts
+  their notices into the file: "strings beam.com | grep -i copyright"
+  shows them.
+  https://github.com/jart/cosmopolitan
+
+OpenSSL 4.0.2 (libcrypto, for the crypto NIF)
+  Copyright The OpenSSL Project Authors.
+  Apache License 2.0 (LICENSE).
+  https://github.com/openssl/openssl
+
+SQLite 3.53.4
+  Public domain. https://sqlite.org/copyright.html
+
+esqlite (the SQLite NIF of Erlang)
+  Copyright Maas-Maarten Zeeman.
+  Apache License 2.0 (LICENSE).
+  https://github.com/mmzeeman/esqlite
+
+WebAssembly Micro Runtime (WAMR) 2.4.5 (the interpreter of the wasm
+application)
+  Copyright The Bytecode Alliance.
+  Apache License 2.0 with LLVM Exceptions (licenses/wamr.txt).
+  https://github.com/bytecodealliance/wasm-micro-runtime
+
+exqlite 0.41.0 (its NIF, for ecto_sqlite3)
+  Copyright 2021 Matthew A. Johnston.
+  MIT License (licenses/exqlite.txt).
+  https://github.com/elixir-sqlite/exqlite
+
+bcrypt_elixir 3.3.2 (its NIF, for phx.gen.auth)
+  BSD-3-Clause, ISC and BSD-4-Clause licenses (licenses/bcrypt_elixir.txt).
+  This product includes software developed by Niels Provos.
+  https://github.com/riverrun/bcrypt_elixir
+
+argon2_elixir 4.1.3 (its NIF, for phx.gen.auth --hashing-lib argon2)
+  Apache License 2.0 (LICENSE). The Argon2 reference code: Copyright
+  2015 Daniel Dinu, Dmitry Khovratovich, Jean-Philippe Aumasson and
+  Samuel Neves, under CC0 1.0 or the Apache License 2.0.
+  https://github.com/riverrun/argon2_elixir
+
+lazy_html 0.1.13, fine 0.1.6 and lexbor (the NIF library in WebAssembly
+of lazy_html in lib/beam_com/priv/nifs; only a program with lazy_html
+0.1.13 contains it)
+  lazy_html and fine: Apache License 2.0 (LICENSE).
+  https://github.com/dashbitco/lazy_html https://github.com/elixir-nx/fine
+  lexbor: Copyright 2018-2020 Alexander Borisov. Apache License 2.0
+  (LICENSE). https://github.com/lexbor/lexbor
+
+The WebAssembly runtime (beam.wasm and beam.mjs in the zip, for
+--target wasm32)
+  Erlang/OTP 29.1.1 and OpenSSL 4.0.2, as above, compiled with
+  Emscripten. The runtime contains the system libraries of Emscripten:
+  - Emscripten: MIT License and University of Illinois/NCSA Open Source
+    License (licenses/emscripten.txt). https://github.com/emscripten-core/emscripten
+  - musl: MIT License (licenses/musl.txt). https://musl.libc.org
+  - LLVM libc++, libc++abi and compiler-rt: Apache License 2.0 with LLVM
+    Exceptions (licenses/llvm.txt). https://llvm.org
+
+Custom builds (build.sh) can also contain:
+  - Hex (HEX=1) and rebar3 (REBAR3=1): Apache License 2.0. The rebar3
+    escript also contains its dependencies, each with its own license
+    (for example certifi: MPL-2.0); see
+    https://github.com/erlang/rebar3/tree/main/vendor.
+  - picosat_elixir (EXTRA_NIFS): Apache License 2.0, with PicoSAT (MIT
+    License, Copyright 2006-2015 Armin Biere, Johannes Kepler University;
+    licenses/picosat.txt).
+  - More OTP applications (OTP_APPS): as Erlang/OTP above.

package/README.md

@@ -0,0 +1,369 @@
+# BEAM.com
+
+Erlang/OTP 29 and Elixir 1.20 in one executable file. The same file runs
+on Linux, macOS, Windows, FreeBSD, NetBSD and OpenBSD, on x86_64 and
+aarch64.
+
+`beam.com` is the Erlang runtime system (ERTS, with the JIT) as one
+[Actually Portable Executable](https://justine.lol/ape.html), made with
+[Cosmopolitan Libc](https://github.com/jart/cosmopolitan). The file is
+also a zip file: the OTP applications, Elixir and your program are in
+it, and they run from there. Nothing is installed, and nothing is
+extracted.
+
+With `beam.com` you can:
+
+- **Run and build programs** with no Erlang or Elixir on the computer: a
+  `.erl` or `.ex` file, or a rebar3 or Mix project with Hex packages.
+  `beam.com INPUT -o OUTPUT` makes one executable that runs on all these
+  systems.
+- **Use Elixir and its tools** from one file: `mix.com`, `iex.com`,
+  `elixir.com`. A Phoenix app with SQLite and `phx.gen.auth` runs from
+  its source, with no C compiler.
+- **Deploy to Cloudflare Workers, Deno Deploy or a web page**:
+  `beam.com INPUT -o DIR --target wasm32` makes one directory that runs
+  the same program on all three, with a second runtime: ERTS compiled to
+  WebAssembly.
+
+The file has the compiler, `crypto` and `ssl` (with OpenSSL), SQLite, and
+a WebAssembly runtime (WAMR). It is about 50 MB.
+
+## Live demos
+
+These run from the WebAssembly runtime of `beam.com`, on the free plans:
+
+- <https://phoenix.fifo.workers.dev> (Cloudflare Workers) and
+  <https://phoenix.one.deno.net> (Deno Deploy): a Phoenix LiveView
+  app with `phx.gen.auth`, Ecto SQLite, PubSub and Presence, from one
+  build ([`examples/phoenix_demo`](examples/phoenix_demo)).
+- <https://livebook.fifo.workers.dev> (Cloudflare Workers, an instance
+  for each visitor) and <https://livebook.one.deno.net> (Deno Deploy):
+  Livebook, with the notebooks of beam.com
+  ([`wasm/livebook`](wasm/livebook)).
+- <https://phx.fifo.workers.dev> (Cloudflare Workers, an instance for
+  each visitor) and <https://sntran.github.io/BEAM.com/phx/> (in the
+  page): `mix phx.new` and a Phoenix app, with nothing to install
+  ([`examples/studio`](examples/studio)).
+- <https://beam.one.deno.net> (Deno Deploy): the Erlang shell, with the
+  VM on the server and a restricted shell for all the visitors
+  ([`examples/worker`](examples/worker)).
+
+## Download
+
+```sh
+curl -fLO https://github.com/sntran/BEAM.com/releases/latest/download/beam.com
+sh ./beam.com --version
+```
+
+On Windows, save the file as `beam.exe`. Each release has `beam.com`
+(with the JIT), `beam-emu.com` (the interpreter: a smaller file that
+starts faster) and `SHA256SUMS`. The prerelease
+[`edge`](https://github.com/sntran/BEAM.com/releases/tag/edge) has the
+`beam.com` of the last merge to `main`.
+
+To check where the file comes from, use the
+[GitHub CLI](https://cli.github.com/): CI signs each `beam.com` of a
+release and of `edge`.
+
+```sh
+gh attestation verify beam.com --repo sntran/BEAM.com
+```
+
+On NetBSD and OpenBSD, start the file with the APE loader
+(`ape-x86_64.elf ./beam.com`): see [`docs/PLATFORMS.md`](docs/PLATFORMS.md).
+
+### A custom build
+
+Do you need more OTP applications (for example `ssh` or `mnesia`), Hex and
+rebar3 in the file, or a file without Elixir, SQLite or WebAssembly? Open
+an issue with the form
+[A custom build of beam.com](https://github.com/sntran/BEAM.com/issues/new?template=custom_build.yml).
+CI builds and tests the file with your choices, and puts it on the issue.
+You need no toolchain. See "A custom build" in
+[`docs/BUILDING.md`](docs/BUILDING.md).
+
+## Quick start
+
+Run a program, and make an executable of it:
+
+```
+$ sh ./beam.com examples/hashsum.erl -- abc
+ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad  abc
+$ sh ./beam.com examples/hashsum.erl -o hashsum.com
+beam.com: wrote hashsum.com (25304313 bytes)
+  release: hashsum 0.1.0
+  applications: beam_com_script kernel stdlib crypto
+  edge: 13 files (62171 bytes) for the WebAssembly runtime
+$ sh ./hashsum.com abc
+ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad  abc
+```
+
+The same for a project: an application directory, a rebar3 project, or a
+Mix project. `beam.com` alone runs the project of the directory.
+
+```sh
+beam.com examples/hexweb -o hexweb.com          # rebar3, with cowboy and jsx from hex.pm
+beam.com examples/greeter_ex -o greeter_ex.com  # Mix, with jason
+beam.com hello.ex -- Alice                      # one Elixir file
+```
+
+Use it as an Elixir installation. A copy or a link of the file with the
+name of a tool is that tool:
+
+```sh
+ln -s beam.com mix.com && ln -s beam.com iex.com
+./mix.com local.hex --force && ./mix.com archive.install hex phx_new --force
+./mix.com phx.new hello --database sqlite3
+cd hello && ../mix.com deps.get && ../mix.com ecto.migrate
+../iex.com -S mix phx.server                     # http://localhost:4000
+```
+
+Make Cloudflare Workers of a program. The same directory runs on Deno:
+
+```sh
+beam.com examples/worker -o worker --target wasm32
+cd worker
+npx workerd serve worker.capnp                   # test on this computer (Workers)
+deno serve -A deno.js                            # or on Deno
+```
+
+One file runs natively and in the WebAssembly runtime. Each executable of
+`-o` also has its edge part, of 40 to 180 KB (`--no-edge` leaves it out).
+A release directory of `mix release` is an input too:
+
+```sh
+beam.com _build/prod/rel/my_app -o my_app.com     # a Phoenix app
+PHX_SERVER=true ./my_app.com                     # natively
+cd worker && BEAM_APP=../my_app.com deno serve -A deno.js   # the same file on Deno
+```
+
+The npm package `beam.com` has the runtime for Node.js, and `npx
+beam.com` (see [npm](#npm)).
+
+See "One file, natively and at the edge" in [`docs/WORKERS.md`](docs/WORKERS.md).
+
+## Publish on GitHub Pages
+
+An Erlang or Elixir app can run in the browser of each visitor, at
+`https://USER.github.io/REPO/`. The code of the app does not change, and
+you need no Erlang, Elixir or Node.js on your computer. Add this file to
+the repository of the app:
+
+```yaml
+# .github/workflows/pages.yml
+name: Pages
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+jobs:
+  pages:
+    uses: sntran/BEAM.com/.github/workflows/pages-app.yml@v0.1.0
+```
+
+Then turn on Pages one time: Settings, Pages, Source "GitHub Actions". The
+`GITHUB_TOKEN` cannot do this step. Until the first release (`v0.1.0`),
+use `@main` in place of `@v0.1.0`: the workflow then uses the `edge`
+build of `beam.com`.
+
+The workflow ([`pages-app.yml`](.github/workflows/pages-app.yml)) builds
+the app with `beam.com --target wasm32`, and publishes the static site
+`DIR/page/`. A Mix project with Phoenix becomes a release first
+(`mix.com release`). Its inputs:
+
+| Input | Default | What |
+|---|---|---|
+| `path` | `.` | The directory of the app. |
+| `beam-com` | the tag of the workflow, else `edge` | The version of `beam.com`. |
+| `deploy` | `true` | `false`: build the site, and do not publish it. |
+
+The workflow that calls it must give `pages: write` and `id-token: write`,
+also with `deploy: false`: else GitHub refuses the run when it starts.
+When the workflow uses `edge` (a pin to a branch, such as `@main`), the
+run shows a warning. A pin to a commit SHA uses the release of that
+commit, and stops with an error when the commit has no release tag.
+Before the build, the workflow checks the SHA-256 of `beam.com` and its
+provenance (`gh attestation verify`). The check stops the build when
+`build.yml` of BEAM.com did not make the file, or when the check cannot
+reach GitHub or Sigstore. It needs no other
+permission.
+
+The app needs an HTTP listener on `PORT` (4000 by default), and only the
+NIFs of the WebAssembly runtime. The limits:
+
+- Each browser has its own copy of the app. Two visitors do not share
+  data.
+- The data stays in the memory of the VM. 30 s after the last tab of the
+  site closes, the data goes, and the next visit starts from the snapshot
+  of the boot.
+- No outgoing TCP: a connection of Erlang gets `econnrefused`.
+- The first visit downloads `beam.wasm` (about 6.5 MB) and `release.bin`
+  (3.5 to 14 MB for a Phoenix app).
+- The browser needs JSPI: Chrome and Edge 137 or later, or Firefox 153
+  or later.
+
+Caution: all the project sites of one GitHub account share one origin
+(`USER.github.io`), also the user site. A page of another site of the
+same account can read the data of the app in the browser: its secret,
+the snapshot of its VM, and its frame. Give an app with private data its
+own custom domain (Settings, Pages, Custom domain).
+
+See "A static site for any app" in [`docs/WORKERS.md`](docs/WORKERS.md).
+
+## npm
+
+This repository is also the npm package `beam.com`, of the same version
+as `beam.com`:
+
+```sh
+npx beam.com app.erl -o app.com
+npx beam.com mix phx.server
+```
+
+The package does not hold `beam.com` (about 50 MB). At the first run,
+`npx beam.com` downloads `beam.com` of the same version from the GitHub
+release, and checks its SHA-256 against the value that the package
+holds. Then the file stays in the cache (`~/.cache/beam.com/npm/`). A
+host that only uses the runtime never downloads it.
+
+- `BEAM_COM`: the path of a `beam.com` to use. Then nothing is
+  downloaded.
+- `BEAM_COM_DOWNLOAD`: the URL of a directory with the file `beam.com`,
+  in place of the GitHub release.
+- `BEAM_COM_CACHE`: the cache directory.
+
+The package also has the WebAssembly runtime, for a native `app.com`.
+In Node.js 25 or later (for JSPI):
+
+```js
+import { boot } from 'beam.com';
+
+const vm = await boot('app.com', { env: { PORT: '4000' } });
+const response = await vm.fetch(new Request('http://localhost/'));
+```
+
+The file must come from `beam.com` of the version of the package: a file
+for another runtime is an error. `release(app)` gives the release of the
+file, without a VM.
+
+`import ... from 'beam.com'` gives the module of the runtime that
+imports it (the conditions of `exports` in `package.json`):
+
+| Runtime (condition) | What |
+|---|---|
+| Cloudflare Workers, with Wrangler (`workerd`) | `serve(app)`, the engine that serves the `app.com` of the project, and the Durable Object `Beam`. |
+| Deno (`deno`) | `serve(app)`, with the same API: the same entry runs on both hosts. |
+| Node.js (`node`) | `boot`, `release`, `appRelease` and `runtimeId`. |
+
+The other modules of the package:
+
+| Import | What |
+|---|---|
+| `beam.com/app-com` | The reader of an `app.com`, for any host: `appRelease(read, size, { runtime })`. |
+| `beam.com/runtime-id` | The identity of this runtime, for `appRelease`. |
+| `beam.com/worker` | The runtime (`worker.js` of Cloudflare Workers). |
+| `beam.com/beam.wasm` | The VM: ERTS built for WebAssembly. |
+
+The same `app.com` runs on Cloudflare Workers, on Deno Deploy and in a
+web page, with the runtime of the package. One entry runs on both hosts:
+
+```js
+import app from './app.com' with { type: 'bytes' };
+import { serve } from 'beam.com';
+export { Beam } from 'beam.com';   // stateful only
+
+const beam = serve(app);
+
+export default {
+  fetch(request, env, ctx) {
+    return beam.fetch(request, env, ctx);
+  },
+};
+```
+
+With the Durable Object `Beam` and its binding, the app is stateful: one
+VM serves all the requests, its timers run between requests, and its
+SQLite storage keeps the database. With no binding, it is stateless:
+each isolate runs its own VM. A project deploys at each git push: the
+build step of the host makes `app.com` (`npx beam.com`), and the host
+runs it. A Phoenix app needs no secret and no variable: the VM
+makes `SECRET_KEY_BASE` one time and keeps it, and `PHX_HOST` is the
+host of the first request. [`examples/phoenix_demo`](examples/phoenix_demo)
+(stateful) and [`examples/worker`](examples/worker) (stateless) are such
+projects, with one-click buttons for both hosts. See "Deploy at
+each git push" in [`docs/WORKERS.md`](docs/WORKERS.md).
+
+The release job of CI makes the generated part of the package
+(`runtime/`, with `scripts/npm.sh`) and publishes it with each tag `v*`.
+
+## Documentation
+
+The site <https://sntran.github.io/BEAM.com/> is Livebook in your
+browser, with these pages as notebooks that run (see
+[`docs/NOTEBOOKS.md`](docs/NOTEBOOKS.md)). The same pages are at
+[`docs/`](https://sntran.github.io/BEAM.com/docs/) as static pages, and
+the Erlang shell in your browser is at
+[`repl/`](https://sntran.github.io/BEAM.com/repl/).
+
+| File | What |
+|---|---|
+| [`docs/PROGRAMS.md`](docs/PROGRAMS.md) | Run and build programs: the inputs, Hex packages, command line programs, native files (`--target`), distributed Erlang, a release in the zip, debugging. |
+| [`docs/ELIXIR.md`](docs/ELIXIR.md) | Elixir programs, the tools (`mix`, `iex`, `elixir`), Phoenix from source, the file watcher. |
+| [`docs/WORKERS.md`](docs/WORKERS.md) | Cloudflare Workers, Deno Deploy and web pages (`--target wasm32`): Durable Objects, Ecto SQLite, snapshots, tenants, limits. |
+| [`docs/NOTEBOOKS.md`](docs/NOTEBOOKS.md) | The documentation as notebooks that run in your browser: a tour of beam.com, the WebAssembly VM, the anatomy of the file, WebAssembly programs, hosts and storage, networking, and building programs. |
+| [`docs/LIBRARIES.md`](docs/LIBRARIES.md) | Crypto and TLS, SQLite, and WebAssembly in Erlang code. |
+| [`docs/SANDBOX.md`](docs/SANDBOX.md) | `--allow-read`, `--allow-write`, `--allow-net`, `--allow-run`: a program that gives up what it does not need. |
+| [`docs/PLATFORMS.md`](docs/PLATFORMS.md) | The status of each system, and the known limits. |
+| [`docs/INTERNALS.md`](docs/INTERNALS.md) | How one file runs everywhere, and the changes to OTP. |
+| [`docs/JIT.md`](docs/JIT.md), [`docs/BENCHMARKS.md`](docs/BENCHMARKS.md) | The JIT in one file for two CPUs, and what each part costs. |
+| [`docs/BUILDING.md`](docs/BUILDING.md), [`docs/TESTING.md`](docs/TESTING.md) | Build BEAM.com, a custom build, CI and the tests. |
+| [`docs/UPSTREAM.md`](docs/UPSTREAM.md) | The problems found in Cosmopolitan, OTP, Emscripten and other projects, with reproducers and fixes. |
+| [`docs/ROADMAP.md`](docs/ROADMAP.md) | What comes next. |
+
+## Examples
+
+| Example | What it shows |
+|---|---|
+| [`examples/hashsum.erl`](examples/hashsum.erl) | A program in one `.erl` file. |
+| [`examples/greeter`](examples/greeter) | An application with a supervisor, as a rebar3 release in the zip of `beam.com`. |
+| [`examples/hexweb`](examples/hexweb) | A web server with Hex packages (cowboy, jsx). |
+| [`examples/greeter_ex`](examples/greeter_ex) | A Mix project with a Hex package in Elixir. |
+| [`examples/toolbox`](examples/toolbox) | A command line program: its entry, `priv` files, and a second VM from its own file. |
+| [`examples/counter`](examples/counter) | Distributed Erlang: a remote shell into a running program. |
+| [`examples/worker`](examples/worker) | The Erlang shell (`shell` of stdlib) on the web, with Cowboy: natively, on Workers, on Deno, and in a web page ([`pages.sh`](examples/worker/pages.sh)). |
+| [`examples/notes`](examples/notes) | Ecto SQLite on a computer, and on Workers with D1 or a Durable Object. |
+| [`examples/phoenix_demo`](examples/phoenix_demo) | Phoenix LiveView with `phx.gen.auth` in a Durable Object. |
+
+## Platforms
+
+| System | Status |
+|---|---|
+| Linux x86_64 and aarch64, WSL2 | ✅ |
+| macOS arm64 and x86_64 | ✅ |
+| Windows x86_64 | ✅ (no port programs) |
+| FreeBSD, NetBSD, OpenBSD 7.3 | ✅ |
+| OpenBSD 7.4 and later | ❌ (not supported by Cosmopolitan) |
+
+CI runs the tests on each system. See
+[`docs/PLATFORMS.md`](docs/PLATFORMS.md) for the details and the known
+limits. The main limits: a native NIF works only when it is linked into
+`beam.com` (another NIF can be a `.wasm` file: see
+[`docs/NIFS.md`](docs/NIFS.md)), and Hex packages are the only
+dependencies of a build (no git dependencies).
+
+## Contributing
+
+See [`CONTRIBUTING.md`](CONTRIBUTING.md). Report a security problem in
+private: see [`SECURITY.md`](SECURITY.md).
+
+## License
+
+BEAM.com is licensed under the [Apache License 2.0](LICENSE). The file
+`beam.com` contains Erlang/OTP, Elixir, Cosmopolitan Libc, OpenSSL,
+SQLite, WAMR and other software, under their own licenses:
+[`NOTICE`](NOTICE) names them, and the license texts are in
+[`licenses/`](licenses) and in the zip of each file.