Enterprise & public sector

Built for closed networks in government, finance and manufacturing

Staff your AI org with on-prem inference servers and local models. Connections that may train on your data are blocked at config time, and licenses are verified offline.

Two ways to deploy

Connected enterprise

Sign in with a company account to get the enterprise plan. Subscription connections are flagged to use business plans (Team, Business, Enterprise).

  • Enterprise-plan accounts
  • 14-day offline grace period
  • Business-plan subscriptions

Closed network · air-gapped

A single signed license file turns on enterprise features. AI runs only on on-prem GPU servers and local models.

  • .moalicense offline license
  • vLLM · SGLang · Ollama
  • No outbound connections needed

What enterprise mode rejects at config time

  • Free-tier connections whose inputs may be used for training
  • Personal trial keys meant for experiments
  • Mock (test-only) connections
  • Configs that relabel a provider to dodge these rules — the real endpoint decides

How license files are verified

  1. Issue

    Organization, seats, term and features are signed together.

  2. Transfer

    It’s one small, human-readable file.

  3. Register

    Use the editor command “Register license file”.

  4. Verify

    Signature and term are checked at startup and hourly; clock rollbacks are detected.

Signatures: ECDSA P-256 + SHA-256 (on Korea’s KCMVP validated algorithm list), Ed25519 optional. Only public keys ship in the editor.

On the roadmap

  • PlannedAudit log
  • PlannedBudgets
  • PlannedTeam dashboard
  • PlannedEnterprise SSO (SAML · OIDC)
  • PlannedSelf-hosted account server for customers

Evaluating MoaEditor for your organization?

Tell us about your team size and network setup, and we’ll design the license and connections with you.

Email sales