Wasmer Docs
WasmerCommunityWAPMWasmer on Github
Search…
Introduction
🏔
Ecosystem
Wasmer Runtime
Getting Started
CLI Usage
Wasmer Features
Building from Source
WAPM
WebAssembly.sh
Wasienv
🔧
Language Integrations
Rust
C/C++
Javascript
Go
Python
PHP
Ruby
Examples
👥
Community
Built with Wasmer
Wasmer Twitter
Wasmer Slack
Wasmer Blog
Wasmer on Github
Powered By GitBook
Wasmer Runtime
Wasmer allows you to run WebAssembly modules either Standalone or Embedded within other languages such as C/C++, Rust, Python, Go, PHP, Ruby...
By design, the environment within which a WebAssembly module runs is completely isolated (or sandboxed) from the native functionality of the underlying host system. This means that by default, Wasm modules are designed to perform nothing more than pure computation.
Consequently, access to "OS"-level resources such as file descriptors, network sockets, the system clock, and random numbers is not normally possible from Wasm.
However, there are many cases in which a Wasm module needs to do more than perform pure computation; they must interact with native "OS" functionality.
Wasmer is designed to provide three key features:
  1. 1.
    Enable programs to run in any programming language
  2. 2.
    Enable extremely portable binaries to run unmodified on any "OS" supported by Wasmer (for example, Linux, macOS, Windows and FreeBSD).
  3. 3.
    Act as a secure bridge for Wasm modules to interact with native "OS" functionality, via Application Binary Interfaces (ABIs) such as WASI and Emscripten (version 1.38.43 and earlier).
For the first case, we offer multiple language integrations, that allow the same Wasm module to be run from within any programming language.
And for the second case, we offer our Standalone Runtime to run Wasm binaries on any platform and chipset.

Important

The term "OS" used above is in quotes to indicate that the native function being called might not actually be provided by the host's operating system.
In reality, native functions always belong to the host environment within which the WebAssembly module is being run, and that could be either the host language's runtime environment (for example, JavaScript, Python, or Ruby), or it might be the actual operating system.
Either way though, from a WebAssembly point of view, we don't need to care too much about this detail. All we need to know is that:
  • The host can provide "imported" functions for the WebAssembly module
  • Via Wasmer's included ABIs, WebAssembly modules can access a set of operating-system-like functions with varying levels of sandboxing

Wasmer Language Integrations

And many more (for which we will be creating docs here soon!)
Let's now get started with the Wasmer Standalone Runtime!
Previous
Introduction
Next
Getting Started
Last modified 2mo ago
Copy link
Contents
Wasmer Language Integrations