Skip to content
  • Our Product
    • Namazu Elements
      • What is Elements?
      • Why open source?
      • Docs
        • Namazu Elements in Five Minutes or Less
        • RESTful APIs Library
        • Security Model
        • Accessing the Web UI (CMS)

    Our Product

    A logomark with three layered rhombuses adorning the lettermark that says Elements in bold all-caps sans-serif letters.
    • What is Namazu Elements? Discover our easy-to-use backend network solution built for online games. Rapidly enables full-scale multiplayer games or online solo adventures.
    • Why open source? Is there a truly open source server backend for connected games? There is now. Download and run a local copy of Namazu Elements and try it for yourself.
    Download Namazu Elements

    Get started

    • Quick start Read our Elements 5-minute quick start guide
    • Documentation Read our developer docs for learning more about Elements
    • RESTful APIs A full list of core API specs for working with the Elements framework
    • Security An overview of the server-authoritative security model of Elements
    • Accessing the CMS Manage your game with ease via the Namazu Elements CMS.

    Co-development Reimagined

    • Best real-time game backends in 2026 If you're researching an alternative to your current backend solution, we've prepared a report of all of the backend solutions on the market in 2026 and how Namazu Elements compares.
      Co-dev

    Recent Posts

    • The watercolor-styled Namazu Studios logo over a giant namazu lurking in the depth
      Namazu Studios Featured in San Diego Business Journal
      22 Sep 2025 Press
    • Namazu Elements 3.1 Released – Service Layer Fixes, Secure APIs, and Steam Bug Fix
      22 Apr 2025 Release Notes
  • Case Studies
  • About Us
  • News
  • Services
  • Book a call
  • Pricing
namazu-studios-logo
Book a call

Getting Started

  • Namazu Elements in Five Minutes or Less
  • Accessing the Web UI (CMS)
  • CMS Feature Overview

Fundamentals

  • Why You Need a Server (and What “Authoritative” Means)
  • Elements as a Game Runtime
  • Where Your Authoritative Code Runs
  • Lifecycles and Flows

General Concepts

  • Overview
  • Custom Elements
  • Data Models
  • Security Model
  • N-Tier Architecture

Namazu Elements Core Features

  • User Authentication / Sign In
    • What is a User?
    • User Authentication in Elements
    • Email Verification
    • Auth Schemes
      • Auth Schemes
      • OAuth2
      • OIDC
  • Features
    • Applications
    • Sessions
    • Users and Profiles
    • Digital Goods
    • Progress and Missions
    • Progress and Missions (3.4+)
    • Leaderboards
    • Matchmaking – Comprehensive Guide
    • Followers
    • Friends
    • Product Bundles and SKUs
    • Receipts
    • Item Ledger
    • Reward Issuances
    • Save Data
    • Metadata
    • Metadata (3.4+)
    • Email Service
    • Queries
    • Web3
      • Wallets
      • Vaults
      • Omni Chain Support
      • Smart Contracts
        • Smart Contracts
  • Queries
    • Advanced Operators
    • Object Graph Navigation
    • Boolean Queries
    • Base Query Syntax
  • Advanced Operators
    • .name
    • .ref

Your Game Code - Adding Custom Elements

  • Custom Code Overview
  • Windows Setup
  • Mac OS Setup
  • Ubuntu Linux Setup
  • Element Anatomy: A Technical Deep Dive
  • Introduction to Guice and Jakarta in Elements
  • Structuring your Element
  • Events
  • Packaging an Element with Maven
  • Deploying an Element
  • Preparing for code generation
  • Properties
  • Websockets
  • RESTful APIs
  • Direct MongoDB Access (3.5+)

Configuration

  • Configuring External URLs for Deployment
  • Matchmaking – Comprehensive Guide
  • Direct Database Access and Batch Configuration
  • Connecting Namazu Elements to a TLS-Enabled MongoDB Replica Set
  • Batch Samples
    • Mission Upload Bash Script Sample
    • Item Upload Bash Script Sample

RESTful APIs

  • Importing into Postman
  • RESTful APIs Library
  • Swagger and Swagger UI

Add-Ons

  • Crossplay
    • Namazu Crossfire (Multiplayer)
    • Deploying Namazu Crossfire in your game
  • Roblox
    • Roblox Overview
    • Secure Player Authentication & Registration
    • Global Matchmaking
    • Roblox Security Best Practices

Game Engine & Client Support

  • Unity
    • Elements Unity Plugin
    • Unity Crossfire Plugin

Troubleshooting

  • Common Issues with Docker
  • Local SDK
    • Unable to deploy application : dev.getelements.elements.sdk.exception.SdkElementNotFoundException
    • Could not load class : java.lang.NoClassDefFoundError
  • Namazu Elements Community Edition
    • Common Issues with Docker
    • Unable to deploy application : dev.getelements.elements.sdk.exception.SdkElementNotFoundException
    • Running in the IDE
      • Exception in monitor thread while connecting to server localhost:27017
      • Could not deployAvailableApplications Jetty server Failed to bind to /0.0.0.0:8080 Address already in use

Releases

  • 3.7 Release Notes
  • 3.6 Release Notes
  • 3.5 Release Notes
  • 3.4 Release Notes
  • 3.3 Release Notes
  • 3.2 Release Notes
  • 3.1 Release Notes
View Categories
  • Home
  • Docs
  • Configuration
  • Configuring External URLs for Deployment

Configuring External URLs for Deployment

Est. read time: 1 min read

Overview #

The Namazu Elements UI is configured via environment variables that control how the frontend locates the REST API, documentation endpoint, CDN, and allowed CORS origins. These variables use the prefix dev_getelements and are resolved at startup.

Elements was originally configured via Java properties files in dot notation. In containerized deployments, environment variables bearing the dev_getelements prefix are automatically converted to dot notation at runtime. Log output reflects this dot-notation form.

Environment Variables #

The following variables configure the Elements UI. All are read at application startup.

VariableDescriptionExample
dev_getelements_elements_api_urlFull external URL for the REST API. Must include the /api/rest path segment. The UI reads this first to initialize the REST client.https://example.com/api/rest
dev_getelements_elements_doc_urlFull URL for the documentation endpoint.https://example.com/doc
dev_getelements_elements_cdn_urlFull URL for the CDN origin. Serves as the origin for static content in the Large Object system.https://example.com/cdn
dev_getelements_elements_cors_allowed_originsComma-separated list of allowed CORS origins. Leave blank to disable CORS header injection.(blank)

Typical Deployment Values #

For a standard deployment at example.com, set the following:

💻
.env
dev_getelements_elements_api_url=https://example.com/api/rest
dev_getelements_elements_doc_url=https://example.com/doc
dev_getelements_elements_cdn_url=https://example.com/cdn
dev_getelements_elements_cors_allowed_origins=

CORS Origin Behavior #

When dev_getelements_elements_cors_allowed_origins is set, the application inspects the incoming Origin request header. If the origin matches one of the listed values, the following response headers are injected:

HeaderValue Set
Access-Control-Allow-OriginValue of the Origin request header
Access-Control-Allow-HeadersX-HTTP-Method-Override, Content-Type, SocialEngine-Secret, Elements-SessionSecret, Authorization
Access-Control-Allow-Credentialstrue
Access-Control-Allow-MethodsGET, POST, PUT, PATCH, DELETE

If the origin does not match, the CORS headers are omitted silently. No error is returned.

Notes #

  • The /api/rest (as well as other similar URI patterns) path segment in dev_getelements_elements_api_url is required and cannot be changed, even though it may appear redundant. This is known technical debt we will address in a future release.
  • Log output shows configuration in dot notation (e.g., dev.getelements.elements.api.url). This is the internal representation after env var prefix conversion and does not require any action.
  • In non-containerized environments, these settings can alternatively be supplied via a Java properties file using the equivalent dot-notation keys or using system defines.
  • On Server startup, Namazu Elements will log all settings and their defaults. The available settings are typically specific to the version you are running. Always refer to the log output for the most accurate list of what Namazu Elements uses.

What are your Feelings
Still stuck? How can we help?

How can we help?

Updated on May 14, 2026
Connecting Namazu Elements to a TLS-Enabled MongoDB Replica SetMatchmaking – Comprehensive Guide
Table of Contents
  • Overview
  • Environment Variables
  • Typical Deployment Values
  • CORS Origin Behavior
  • Notes
  • Documentation
  • Terms of Service
  • Privacy Policy
  • Contact us
  • Linkedin
  • Join our Discord

Namazu Studios LLC is powered by Namazu Elements, an open source modular backend framework for connected games.

Namazu Elements
  • Download
  • About Elements
  • Open source
  • Documentation
  • Support
Namazu Studios
  • Case Studies
  • About Us
  • News
Best realtime game backends 2026
Get in Touch
  • info@namazustudios.com
  • Book a call
  • (619) 862-2890
  • Linkedin
  • Discord

©2008-2026 Namazu Studios. All Rights Reserved.