Skip this step when deploying from a template — go directly to [Step 2](#step-2-deploy-the-application).
Required: [Rust and Cargo](https://rustup.rs). On Windows, also install [Visual Studio Build Tools](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2022) with the **Desktop development with C++** workload.
1. Add the Wasm compilation target: ```sh theme={null} rustup target add wasm32-wasip2 ``` 2. Scaffold an application from the `http-base` template: ```sh theme={null} npm create fastedge-app@latest my-rust-app -- --rust --template http-base --no-verify ``` 3. Build the Wasm binary: ```sh theme={null} cd my-rust-app cargo build --release ```The Wasm file is written to `./target/wasm32-wasip2/release/basic_wasi_http.wasm`. Upload this file in Step 2.
Required: [Node.js](https://nodejs.org).
1. Scaffold an application from the `http-base` template: ```sh theme={null} npm create fastedge-app@latest my-first-app -- --javascript --template http-base --no-verify ``` 2. Build the Wasm binary: ```sh theme={null} cd my-first-app npm install npm run build ```The Wasm file is written to `./wasm/basic-http.wasm`. Upload this file in Step 2.
Two deployment methods are available: from a custom binary built in Step 1, or from a preconfigured template — no binary is required for templates.
### From a binaryUse this method when deploying a Wasm binary built with the Rust or JavaScript SDK in Step 1.
1. In the [Gcore Customer Portal](https://portal.gcore.com), navigate to **FastEdge** > **HTTP Applications** > **Applications** and click **Create new application**.
2. On the **Create an application** page, click the **Upload binary** card.
3. In the **Upload binary** dialog, click **Click to upload or drag and drop** and select the `.wasm` file. The portal processes the upload and opens the **Deploy application** page.
4. Enter a **Name** for the application and an optional description.
5. (Optional) In the **Response headers** section, click **Add response header** to add static headers to every HTTP response. Common uses: CORS (`Access-Control-Allow-Origin: *`), security headers (`X-Frame-Options: DENY`), custom cache directives.
6. (Optional) In the **Environment variables** section, click **Add environment variable** and enter key-value pairs. The application reads these values at runtime using the FastEdge SDK — for example, `getEnv('API_ENDPOINT')` in JavaScript or `std::env::var("API_ENDPOINT")` in Rust. Use for configuration that changes between deployments without rebuilding the binary.
7. (Optional) In the **Secrets** section, click **Add secret** to attach an encrypted value for sensitive data such as API keys or tokens. The app accesses it as a regular environment variable — the key set here becomes the variable name. A secret must exist in [Secrets Manager](/fastedge/secrets-manager/manage-secrets) before it can be attached.
8. (Optional) In the **Edge Storage** section, click **Add Edge Storage** to attach a key-value store the application can query at the edge without hitting the origin server. The store must exist on the [Edge Storage](/fastedge/kv-stores/manage-kv-store) page before it can be attached.
9. Click **Save and deploy**.
The application details page opens with the deployment URL.
### From a template
Use this method to deploy a built-in or custom template without writing or building any code.
1. In the Customer Portal, navigate to **FastEdge** > **HTTP Applications** > **Applications** and click **Create new application**.
2. Scroll to the **Create from a template** section and select a template. Built-in templates are **Geolocation-based redirect** and **Markdown renderer**. To deploy from a custom template, create it first on the **HTTP Applications** > **Templates** page as described in [custom templates](/fastedge/create-manage-templates).
3. Enter a **Name** for the application and an optional description.
4. Fill in the **Template environment variables** required by the selected template:
**Markdown renderer**
* **BASE** (required): Base URL for Markdown source files. Example: `https://raw.githubusercontent.com/G-Core/FastEdge-sdk-js/main/`
* **HEAD** (optional): HTML inserted into the `` tag. Example: ``
**Geolocation-based redirect**
* **DEFAULT** (required): Fallback redirect URL for visitors whose country does not match any rule. Example: `https://example.com/fallback`
* In the **Environment variables** section, add ISO 3166-1 alpha-2 country codes as keys with redirect URLs as values. Example: key `LU`, value `https://example.com/luxembourg`.
5. (Optional) Configure additional sections:
* **Response headers**: static headers added to every response (e.g., CORS or security headers).
* **Environment variables**: runtime key-value pairs the application reads via the SDK. These are separate from the template-defined variables above.
* **Secrets**: encrypted values for sensitive data such as API keys. The app accesses a secret as an environment variable using the key name set here. Requires an existing secret in Secrets Manager.
* **Edge Storage**: a key-value store the app queries at the edge. Requires an existing store on the **FastEdge** > **Edge Storage** page.
6. Click **Save and deploy**.
The application details page opens with the deployment URL.
## Step 3. Test the application
Click the URL at the top of the application details page to open the application in a browser, or test with curl:
```sh theme={null} curl -i https://To find the URL later, navigate to **FastEdge** > **HTTP Applications** > **Applications** and check the **URL** column.
Set this variable before running the examples:
```bash theme={null} export GCORE_API_KEY="{YOUR_API_KEY}" ``` ## Step 1. Build a Wasm binaryBuild the binary using the Rust or JavaScript SDK. Set `WASM_PATH` at the end of the tab — it is used in Step 2.
Required: [Rust and Cargo](https://rustup.rs). On Windows, also install [Visual Studio Build Tools](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2022) with the **Desktop development with C++** workload.
```bash theme={null} rustup target add wasm32-wasip2 npm create fastedge-app@latest my-rust-app -- --rust --template http-base --no-verify cd my-rust-app && cargo build --release export WASM_PATH="./target/wasm32-wasip2/release/basic_wasi_http.wasm" ```Required: [Node.js](https://nodejs.org).
```bash theme={null} npm create fastedge-app@latest my-first-app -- --javascript --template http-base --no-verify cd my-first-app && npm install && npm run build export WASM_PATH="./wasm/basic-http.wasm" ```Deploying requires two calls: upload the binary, then create the application referencing the returned binary ID.
**1. Upload the binary** | Parameter | Required | Description | | ------------ | -------- | --------------------------------------------- | | Request body | Yes | Raw Wasm binary as `application/octet-stream` |The API returns:
```json theme={null} {"id": 4683, "api_type": "wasi-http", "status": 1, "checksum": "ba9dae6f9e5850833cd1929170916f2b"} ``` ```bash theme={null} export BINARY_ID="{id}" # replace with the id from the response above ```The API returns:
```json theme={null} {"id": 2543, "name": "my-edge-app", "url": "https://my-edge-app-1000503.fastedge.app", "status": 1, "binary": 4683, "api_type": "wasi-http", "plan": "Free"} ```The deployment URL becomes active within a few seconds of creation. Send a request to the `url` from the create-app response:
```bash theme={null} curl -i https://The `http-base` template returns a plain-text response:
``` HTTP/1.1 200 OK content-type: text/plain;charset=UTF-8 Hello from FastEdge! ```