Deployment Modes

NExS offers four deployment modes that control who can access your app and how data persists. Choose the right mode based on your use case.

Mode Overview

Open Mode

Open mode is the default. Anyone with the URL can use the app, and each session is independent.

Configuration

No mode setting needed—Open is the default.

Behavior

• No login required
• New instance created each time someone opens the app
• Data exists only while the browser tab is open
• Closing or reloading starts fresh

When to Use

Open mode works well for public-facing tools like calculators, quote generators, and interactive demonstrations. It’s ideal for embedded widgets where each visitor should work independently with their own fresh instance.

Personal Mode

Personal mode requires users to log in. Each user’s data persists permanently in their own private instance.

Configuration

Behavior

• Users must log in to NExS platform
• Each user has their own copy of the app
• Data persists until the app is deleted
• Users can return and continue where they left off

When to Use

Personal mode is perfect for tools where users need to save their work—expense trackers, personal dashboards, goal tracking tools, or any app that benefits from persistent user data. For example, an employee could enter their monthly expenses and return anytime to update or review their data.

Team Mode

Team mode creates a single shared instance that specified team members can access.

Configuration

Behavior

• Users must log in with an email on the accessList
• Everyone sees and edits the same data
• Changes by one user appear for all users
• Data persists permanently

Access Control

Restrict access to specific views with readACL and writeACL:

• readACL — Who can see this view
• writeACL — Who can edit inputs in this view

When to Use

Team mode suits internal dashboards, shared planning tools, status boards, and collaborative data entry. For example, a project status dashboard where team members update their sections while managers view the overview.

Access Code Mode

Access Code mode allows collaborative access without requiring NExS accounts. Users enter a code instead of logging in.

Configuration

Behavior

• Users enter an access code (like a password)
• All code holders share the same instance
• Changes appear in real-time for all users
• Data persists permanently
• Different codes can have different permissions

View Access by Code

Restrict views to specific access keys:

In this example:

• Judges see “Judge Panel” (requires their code)
• Anyone can see “Scoreboard” (marked public)

When to Use

Access Code mode excels at competition scoring, event check-ins, collaborative workshops, and role-based forms. For example, in a cooking competition, three judges log in with their codes to enter scores while a public scoreboard displays results in real-time without requiring a code.

Security: Allowed Origins

By default, NExS apps can be embedded on any website. Use allowedOrigins to restrict embedding:

Examples

Other patterns:

• www.mycompany.com — Only on specific server
• *.mycompany.com, *.partner.com — Multiple domains
• https://*.mycompany.com — HTTPS only

This prevents others from embedding your app on unauthorized sites.

Choosing the Right Mode

Combining Features

Public View + Private Admin

Admins enter scores; everyone else sees the public scoreboard.

Team Mode with Role-Based Access

All team members see the Overview. Only the manager can access Settings.

Next Steps

• Views and Layouts — Configure what users see
• Inputs and Forms — Control who can edit what
• UI Components — Add navigation and actions