Defense & intelligence · Managed environment

Wargaming & Simulation Sandbox

Compartmented environments for running wargames and simulations, built and run for each exercise

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

Moraph builds and operates the virtual environments your organization uses for wargames and large simulations: compute that scales for the event, the simulation software you license, and separation between exercises so data from one cannot be seen from another. Each exercise is provisioned from an approved template, run, and then archived or destroyed according to your rules. Your organization decides who takes part, what data goes in and what happens to the results; Moraph runs the environment under your authority.

The problem it solves

Wargaming and simulation teams need large amounts of compute for short periods, and each event brings its own participants, scenarios and data sensitivities. Environments are often assembled by hand for each exercise, left running afterwards, and shared between events in ways that make it hard to show that one exercise's data could not be reached from another. Aggregated simulation results can reveal more about capabilities than any single input, so who can see what, and what is kept, matters as much as the compute.

  • Each exercise environment is built by hand, so builds differ and take staff time away from the event
  • Compute is either over-provisioned all year or short when a large event runs
  • Separation between exercises and between participant cells is hard to evidence
  • Results and logs are kept or deleted inconsistently after an event ends

Who uses it

  • Wargaming and analysis organizations that plan and run exercises
  • Modeling and simulation program offices
  • Exercise directors and control cells who run events
  • Information system security managers and authorizing officials responsible for the environment
  • Security officers who manage compartmented access and classification guidance

Requirements it supports

DoD Instruction 8510.01, Risk Management Framework for DoD SystemsCNSSI No. 1253, Security Categorization and Control Selection for National Security SystemsNIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and OrganizationsDoD Instruction 5000.61, DoD Modeling and Simulation Verification, Validation, and AccreditationDoD Manual 5200.01, DoD Information Security ProgramExecutive Order 13526, Classified National Security Information

The product supports these requirements; meeting them remains your organization’s responsibility.

Responsibilities

Who is responsible for what

Moraph builds and runs the environments; compute, cloud and simulation software come from their providers under their own terms; your organization owns the exercises, the data and the decisions about them.

AreaMoraphInfrastructure and software providersYour organization
Hardware, cloud and software licensingSizes the platform, supplies or resells infrastructure where contracted, and installs licensed softwareSupply hardware, cloud services and simulation software under their own termsHolds or funds simulation software licences and approves capacity plans
Platform availabilityOperates the shared platform and each exercise environmentKeep their hardware, cloud services and software available under their own commitmentsProvides facilities and network for on-premises deployments
Templates and configurationBuilds and maintains templates and the baselineProvide the underlying configuration optionsApproves templates and any departure from them
Identity and accessCreates and removes accounts from approved rostersNone beyond their own administrative controlsApproves rosters and confirms access eligibility
MonitoringMonitors health, capacity and security events and forwards logsMonitor their own infrastructure and servicesReviews escalated security events
Incident responseResponds under the agreed runbooks and reports each incidentRespond to failures in their products or servicesLeads security incident decisions and any reporting
ChangesRaises, tests and applies approved changesAnnounce changes to their products and servicesApproves changes through the ISSM and, during events, the exercise director
Patches and updatesTests and applies patches and software updates on the agreed schedulePublish patches and new versionsAgrees the schedule and approves exceptions
Exercise data and resultsLoads, exports, archives or destroys as instructedNoneDecides what data is used, who sees results and what is kept
User supportRuns the service desk for participants and control cellsSupport their own products through MoraphBriefs participants and provides exercise-specific guidance

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of the platform itself, which belongs to its vendor.

  1. Step 1

    Onboarding tracker

    During implementation, the platform, templates and pilot exercise are tracked with an owner on both sides.

    WorkstreamMoraph ownerYour ownerStatus
    Exercise program reviewSolution architectAnalysis team leadComplete
    Compartment model and control mappingSecurity leadISSMIn review
    Template: seminar gamePlatform engineerExercise directorApproved
    Template: large computer-assisted exercisePlatform engineerExercise directorWaiting on software licences
    Separation testingSecurity leadSecurity officerScheduled
    Pilot exerciseService managerExercise directorNot started
    During implementation, the platform, templates and pilot exercise are tracked with an owner on both sides.

  2. Step 2

    An exercise request

    Each request names the template, dates, cells and data, and shows the approvals it needs before Moraph builds.

    EX-0219 · Example Exercise Northwind (fictional)

    Template
    Large computer-assisted exercise
    Participant cells
    4 plus control cell
    Participants on roster
    86
    Reserved compute
    Fictional sample allocation
    Classification guidance
    Awaiting security officer

    Approvals

    • Data sets approved by data owner
    • Roster approved by exercise director
    • Classification guidance pending with security officer
    • No departure from template; ISSM approval not required
    Each request names the template, dates, cells and data, and shows the approvals it needs before Moraph builds.

  3. Step 3

    Build and separation check

    Each environment is built from its template and tested for separation before participants are given access.

    EX-0219 · Build record

    1. Environment built from approved templateMoraph platform engineer
    2. Simulation software and approved data sets loadedMoraph platform engineer
    3. Accounts created from approved rosterMoraph platform engineer
    4. Separation tests between cells and exercises passedMoraph security lead
    5. Build record reviewed and environment releasedExercise director
    Each environment is built from its template and tested for separation before participants are given access.

  4. Step 4

    Alert triage during an event

    While an exercise runs, Moraph triages platform alerts and keeps the control cell informed.

    AlertExerciseDescriptionSeverityOwnerStatus
    PA-1184EX-0219Compute use near reserved limitMediumMoraph engineerDirector informed
    PA-1181EX-0219Simulation server restartedHighMoraph engineerResolved; control cell informed
    PA-1177EX-0214Sign-in failures for one participantLowService deskResolved
    PA-1172PlatformPatch due on hypervisor hostsMediumService managerChange raised for after event
    While an exercise runs, Moraph triages platform alerts and keeps the control cell informed.

  5. Step 5

    Close-out

    When the exercise ends, access is removed, approved results are exported and the environment is archived or destroyed as instructed.

    Close-out · Example Exercise Seaward (fictional)

    Participant access
    Removed at agreed end
    Results exported
    To designated repository
    Export approved by
    Exercise director and security officer
    Disposition
    Destroy
    Destruction record
    Awaiting security officer confirmation

    Removed

    • Virtual machines and storage volumes
    • Exercise network segment
    • Participant accounts and keys
    When the exercise ends, access is removed, approved results are exported and the environment is archived or destroyed as instructed.

  6. Step 6

    Monthly service review

    Each month Moraph reports on exercises supported, incidents and changes, and agrees actions with your program office.

    Monthly service review · Fictional sample month

    Exercises supported
    3
    Incidents
    1 (closed)
    Changes applied
    5 of 5 approved
    Overdue close-outs
    None
    Calendar conflicts
    2 events overlap next quarter

    Actions agreed

    • Program office to confirm priority between overlapping events
    • Moraph to propose additional reserved capacity options
    • ISSM to review updated seminar game template
    Each month Moraph reports on exercises supported, incidents and changes, and agrees actions with your program office.

Workflows

The principal workflows

  1. Request an exercise

    An exercise director requests an environment from the catalog of approved templates, with dates, participant cells, simulation software and the data that will be loaded.

    • Director selects a template and states dates, scale and participant cells
    • Security officer confirms the classification guidance and compartments
    • Data owner approves the data sets to be loaded
    • ISSM approves any departure from the template
    • Moraph schedules the build and reserves compute

  2. Provision

    Moraph builds the exercise environment from the approved template as a separate compartment, with its own network segment, accounts and storage, and verifies it before participants arrive.

    • Environment built from the template as an isolated compartment
    • Simulation software and approved data loaded
    • Participant accounts created from the approved roster
    • Separation between cells and from other exercises verified
    • Environment handed to the exercise director with a build record

  3. Run

    During the event, compute scales within the reserved limits, Moraph monitors the environment, and the control cell manages the scenario without platform work getting in the way.

    • Compute scaled up or down within the reserved limits
    • Platform health and capacity monitored throughout
    • Participant support requests handled by the service desk
    • Any change during the event approved by the exercise director and ISSM
    • Incidents handled under the agreed runbooks

  4. Close out

    When the exercise ends, results are delivered to the people entitled to them, and the environment is archived or destroyed according to your rules, with a record of what was done.

    • Participant access removed at the agreed end time
    • Results and logs exported to the data owner through approved channels
    • Environment archived or destroyed as instructed
    • Destruction or archive record produced for the security officer
    • Lessons and capacity use reviewed for the next event

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Exercise director

Exercise director, wargame lead, analysis team lead

Owns the event: what is simulated, who takes part and what happens to the results.

Sees

  • Their exercises, templates available and reserved capacity
  • Participant rosters and cell structure
  • Build records and environment status
  • Service requests raised during the event

Does

  • Requests an environment from a template, with dates and scale
  • Approves the participant roster and cell structure
  • Directs the control cell's views across cells
  • Approves changes requested during the event
  • Decides, with the data owner, which results are exported

Cannot

  • Load data sets that their owners have not approved
  • Change the security baseline without ISSM approval
  • Extend an exercise's access beyond the agreed end without the security officer
Approvals
Their requests need security officer confirmation of classification guidance and ISSM approval for any departure from the template.
Notified about
Build complete, capacity close to reserved limits, open service requests during the event and close-out records.

Security officer

Security manager, special security officer, information security officer

Makes sure each exercise is set up and closed out in line with the classification guidance and compartments that apply.

Sees

  • Classification guidance and compartments for each exercise
  • Rosters and the access each participant holds
  • Separation test results for each build
  • Archive and destruction records

Does

  • Confirms the classification guidance and compartments for each request
  • Checks rosters against access eligibility
  • Approves extensions to participant access
  • Confirms close-out: archive or destruction of the environment
  • Reviews access logs after the event

Cannot

  • Build or change environments
  • Approve their own access
  • Edit or delete audit records
Approvals
Confirms each exercise's guidance and compartments and signs off close-out.
Notified about
New exercise requests, roster changes, separation test failures and close-out records waiting for confirmation.

Participant

Player, analyst, subject-matter expert, control cell member

Takes part in the exercise, using the simulation from within their assigned cell.

Sees

  • The simulation and data available to their cell
  • Their own account and session information
  • Event support contacts

Does

  • Signs in for the duration of the exercise
  • Runs and interacts with the simulation within their cell
  • Raises support requests to the service desk
  • Saves work to the exercise's storage

Cannot

  • See other cells' views unless the director grants it
  • Reach other exercises or the internet from the environment
  • Copy data out except through approved export
Approvals
Their access is approved through the roster by the exercise director and checked by the security officer.
Notified about
Account ready, exercise start and end times, and responses to their support requests.

ISSM

Information system security manager, ISSO

Answers for the security of the environment and controls changes to its baseline and templates.

Sees

  • Templates, baselines and their change history
  • Change requests and patch status
  • Separation test results and audit logs
  • Control mappings and evidence

Does

  • Approves templates and changes to them
  • Approves departures from a template for a specific exercise
  • Approves patch schedules and emergency changes after review
  • Reviews security alerts escalated by Moraph
  • Prepares continuous monitoring submissions with Moraph's evidence

Cannot

  • Approve a change they raised themselves without a second approver
  • Edit or delete audit records
  • Load exercise data
Approvals
Approves templates, baseline changes, patch schedules and security exceptions.
Notified about
Changes awaiting approval, separation test failures, security alerts and patches due.

Moraph platform engineer

Moraph platform and simulation environment engineers (US citizens with the clearances the contract requires)

Builds, monitors and closes out exercise environments and keeps the shared platform healthy.

Sees

  • Platform health, capacity and reservations
  • Build and close-out tasks
  • Platform logs and alerts
  • Approved changes and maintenance windows

Does

  • Builds environments from approved templates and runs separation tests
  • Scales compute within reserved limits during events
  • Monitors the platform and triages alerts
  • Applies approved patches and changes
  • Archives or destroys environments as instructed and produces the record

Cannot

  • View exercise scenarios, results or participant work
  • Add participants or change rosters
  • Make an unapproved change, except emergency actions recorded and reviewed under the incident process
Approvals
Planned changes need ISSM approval; changes during an event also need the exercise director.
Notified about
Builds scheduled, platform alerts, capacity near reserved limits and close-out instructions.

Moraph service manager

Moraph service delivery manager

Is accountable for the service across all exercises, and runs the monthly service review.

Sees

  • The exercise calendar and capacity reservations
  • Service performance, incidents and requests
  • Change and patch calendars

Does

  • Plans builds and capacity against the exercise calendar
  • Runs the monthly service review and agrees actions
  • Coordinates requests between your teams and Moraph engineers
  • Manages escalations to infrastructure and software providers

Cannot

  • Open exercise content
  • Approve changes on your organization's behalf
  • Change rosters
Approvals
Nothing they do changes an environment without the approvals above.
Notified about
Calendar conflicts, major incidents, escalations and overdue close-outs.

Auditor (read-only)

Inspector general staff, security control assessor, internal auditor

Reviews how exercises were built, accessed and closed out, without being able to change anything.

Sees

  • Build records, separation test results and close-out records
  • Rosters and access logs within the scope granted
  • Change and patch history
  • Control evidence and service reports

Does

  • Searches and reads records within their scope
  • Exports records, with each export logged
  • Records review notes where enabled

Cannot

  • Change, approve or delete anything
  • See exercise content unless separately granted
  • Keep access after it expires
Approvals
Their access is approved by the ISSM with a scope and an end date.
Notified about
Nothing by default; access granted and expiring is confirmed to the ISSM.

Permissions at a glance

ActionDirectorSecurity off.ParticipantISSMMoraph eng.Service mgrAuditor
Request an exercise environmentOwn work onlyView onlyNo accessView onlyNo accessView onlyNo access
Approve participant rosterApprovesApprovesNo accessNo accessNo accessNo accessView only
Approve data sets to loadOwn work onlyView onlyNo accessNo accessNo accessNo accessView only
Build environment from templateView onlyView onlyNo accessView onlyFullView onlyView only
Run the simulationFullNo accessOwn work onlyNo accessNo accessNo accessNo access
Change templates or baselineNo accessNo accessNo accessApprovesOwn work onlyView onlyView only
Scale compute during an eventApprovesNo accessNo accessNo accessFullView onlyNo access
Apply patches and updatesNo accessNo accessNo accessApprovesFullView onlyView only
Export results at close-outApprovesApprovesNo accessNo accessOwn work onlyNo accessView only
Archive or destroy environmentApprovesApprovesNo accessView onlyFullView onlyView only
View audit logsView onlyFullNo accessFullView onlyNo accessView only
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Moraph engineers build and run environments but do not see exercise scenarios, results or participant work; exports at close-out are approved by the exercise director and security officer and handed over through your approved channels.
  • No single person controls an exercise end to end: the director requests, the security officer confirms guidance and close-out, the ISSM approves departures from the baseline, and Moraph builds.
  • Roles are configured with you. Rosters can come from your identity provider's groups, and participant access ends automatically at the agreed close of the exercise.
  • Work on federal and defense tickets is done only by US citizens holding the clearances the contract requires, and work in classified environments happens under your organization's authority.

Features

What it does

Approved templates

Exercise environments built from templates your ISSM has approved, so each build matches a known baseline.

Compartment per exercise

Each exercise runs in its own isolated network segment, accounts and storage, separate from every other exercise.

Cell separation

Participant cells inside an exercise can be separated from one another, with the control cell given the views the director decides.

Scalable compute

Compute reserved for each event and scaled within those limits, so large simulations get capacity when they run without paying for it all year.

Simulation software hosting

The simulation and wargaming software your organization licenses or develops is installed and maintained in each environment.

Data loading controls

Only data sets approved by their owner are loaded into an exercise, and every load is recorded.

Roster-based access

Participant accounts are created from an approved roster and removed when the exercise ends.

Archive or destroy

At close-out the environment is archived or destroyed according to your instruction, with a record of what was kept and what was removed.

Build records

Each environment's template, configuration, software versions and data loads are recorded, so results can be traced to the setup that produced them.

Exercise calendar

Planned events, reserved capacity and build dates in one calendar, so conflicts are seen early.

Event support

A service desk for participants and the control cell during the event, with escalation to Moraph engineers.

Control evidence

Control mappings and evidence for your RMF package, including separation testing results for each build.

Integrations

How it connects to your systems

Connects toHowWhat flows
Simulation and wargaming softwareThe commercial, government or in-house simulation software your organization licenses or develops, installed in each environment under its own licence terms.In: software packages, licences and scenario files supplied by your organization.
Identity providerParticipants sign in through your identity provider, including certificate-based sign-in where required, and rosters can follow its groups.In: user identity, attributes and group membership.
Data sourcesApproved data sets for an exercise, such as terrain, order-of-battle or scenario data, loaded through your approved transfer process.In: data sets approved by their owners, with each load recorded.
Results repositoryAt close-out, results and logs are delivered to the repository or analysis environment your organization designates.Out: results, logs and build records approved for export.
Security monitoringPlatform and access logs forwarded to your security operations tooling.Out: audit, access and platform logs.
Moraph Work APIExercise requests, service tickets and change records available to your service management tools.Out: requests, tickets, changes and service metrics.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Single sign-on

Participants and staff sign in through your identity provider, so your authentication policies apply.

Compartmented access

Each exercise and each cell is separated by network, accounts and storage, and access follows the approved roster.

Encryption and keys

Data is encrypted at rest and in transit, with keys Moraph staff cannot use without explicit, time-bound authorization from your organization.

Complete audit trail

Builds, sign-ins, data loads, changes, exports and destruction are logged with the person and time, and cannot be edited.

Cleared US staff

Federal and defense work is handled only by US citizens with active clearances, and environments are hosted only in the United States.

Tested releases

Security testing gates every change to Moraph's templates and tooling, and a software bill of materials is kept for the components Moraph supplies.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

10 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Exercises

Exercise calendar and capacity

For exercise directors and program office

Planned exercises with build dates, reserved compute and conflicts between events.

Break down by
Month, Exercise, Template, Reserved capacity
Delivered as
Live dashboard
Used for
Planning events so capacity and build time are available when needed.

Build record

For exercise director, ISSM and security officer

For one exercise, the template, configuration, software versions, data loads and separation test results.

Break down by
Exercise, Component, Test result
Delivered as
PDF; live view
Used for
Confirming the environment was built as approved and tracing results to their setup.

Close-out record

For security officer and auditors

What was exported, to whom, and whether the environment was archived or destroyed, with dates and approvers.

Break down by
Exercise, Disposition, Approver
Delivered as
PDF
Used for
Evidencing that exercise data was handled as instructed after the event.

Compute use by exercise

For program office

Compute reserved and used for each exercise over its duration.

Break down by
Exercise, Day, Resource type
Delivered as
Live dashboard; CSV export
Used for
Sizing future events and allocating costs between programs.

Service

Monthly service review

For program office and ISSM

Exercises supported, incidents, changes, support requests and actions agreed at the last review.

Break down by
Month, Exercise, Incident severity, Action owner
Delivered as
PDF; review meeting
Used for
Holding Moraph to account and agreeing priorities.

Event support log

For exercise directors

Support requests raised during each event, how long they were open and how they were resolved.

Break down by
Exercise, Request type, Cell, Status
Delivered as
Live view; CSV export
Used for
Reviewing participant experience and fixing recurring problems before the next event.

Change and patch record

For iSSM and auditors

Every change to templates and the platform, with who raised, approved and applied it.

Break down by
Change type, Approver, Template, Outcome
Delivered as
Live view; CSV export
Used for
Evidencing that templates and the platform change only through approved requests.

Security and audit

Separation testing

For iSSM and security officer

Results of separation tests between exercises and between cells for each build.

Break down by
Exercise, Test, Result, Build date
Delivered as
Live view; PDF export
Used for
Showing that compartments were in place before participants arrived.

Roster and access review

For security officer

Each participant's access by exercise and cell, when it started and when it was removed.

Break down by
Exercise, Cell, User, Removal date
Delivered as
Live view; CSV export
Used for
Confirming that access matched the roster and ended on time.

Audit trail extract

For security officer, ISSM and auditors

Who signed in, loaded data, changed, exported or destroyed what, and when, for a selected exercise or period.

Break down by
Exercise, User, Action, Date range
Delivered as
On request; CSV and PDF export
Used for
Answering inspection and investigation requests without assembling logs by hand.

Exports, access and evidence

  • Reports can be exported to CSV and summary reports to PDF, and scheduled to the people entitled to see them.
  • Reports respect each viewer's role: directors see their own exercises, security officers see rosters and close-out, and Moraph staff see platform and service data without exercise content.
  • Requests, tickets and changes are available through the Moraph Work API for your own service management and reporting tools.
  • Audit and close-out records can be run as of a past date and give the same result each time; running and exporting a report is itself logged.
  • In classified deployments, reports are produced and kept inside the environment and leave it only through your approved channels.

Deployment

Where and how it runs

On your premises

Built in your data center or enclave, including classified environments, and operated under your organization's authority by cleared Moraph staff where the contract provides for it.

US government cloud region

Built in a US government cloud region your organization has approved, hosted only in the United States, with compute reserved for each event.

Hybrid

A standing on-premises platform that draws on approved cloud capacity for the largest events, scoped in the proposal.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Discovery

We review your exercise program, simulation software, typical event sizes and classification needs. We need your recent and planned exercises and a contact from your security office.

Platform design

The shared platform and compartment model are designed for your network and security domain, with the control mapping your ISSM needs.

Templates

Exercise templates are built for your common event types and simulation software, tested, and approved by your ISSM.

Build and separation testing

The platform is built on your premises or in a US government cloud region, and separation between environments is tested and documented.

Pilot exercise

A first exercise is run end to end, from request to close-out, and the process adjusted with your exercise and security staff.

Authorization support and operations

We supply evidence for your assessment, then move to steady-state operations with the exercise calendar, runbooks and monthly service reviews.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • Moraph is not the maker of the simulation software, hardware or cloud services. Their own service commitments, roadmaps and outages apply, and licences are subject to their terms.
  • Moraph does not hold an accreditation or authorization for the environment. Your authorizing official decides whether it operates; Moraph maps controls and supplies evidence to support that decision.
  • Work in classified environments happens under your organization's authority and only where the contract provides for it, by US citizens with the required clearances.
  • Moraph does not design scenarios, adjudicate games or analyze results. Exercise design, play and conclusions belong to your organization.
  • Verification, validation and accreditation of models and simulations under DoD Instruction 5000.61 remain your organization's responsibility; Moraph keeps the build records that support it.
  • Compute is available within the capacity reserved for each event; exceeding it depends on what the platform or cloud provider can supply at the time.
  • Moving data between security domains is not included; it uses the cross-domain solution your organization has approved.
  • Classification guidance and decisions about aggregated results are your security office's responsibility; the environment enforces the separation they specify.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. Give us a recent exercise and review how it would be requested, built, run and closed out
  2. Ask to see a sample build record and separation test results
  3. Check how participant access is created from a roster and removed at the end
  4. Walk through an archive and a destruction close-out with your security officer
  5. Confirm that Moraph engineers can operate environments without seeing exercise content
  6. Review the responsibilities table against your operating model and contract

Questions

Frequently asked questions

Who owns the exercise data and results?

Your organization does. Moraph operates the environments and does not view scenarios or results. What is kept and what is destroyed after each exercise is your decision.

Can Moraph operate environments at a classified level?

Where your contract provides for it, cleared Moraph staff operate environments in classified enclaves under your organization's authority. Moraph does not hold an accreditation of its own; your authorizing official decides whether the environment operates.

Which simulation software can we use?

The commercial, government or in-house software your organization licenses or develops, subject to its licence terms and to the environment it needs. It is assessed during discovery.

How is one exercise kept apart from another?

Each exercise runs in its own network segment, accounts and storage, built from an approved template, and separation is tested and recorded before participants are given access.

How is it priced?

As a managed service, usually driven by the standing platform, the compute reserved for events and the number of exercises supported, with design and templates charged separately. See Working with Moraph for what drives a quotation.

Is there an accessibility conformance report?

Ask for one through the procurement request form at /how-to-buy/request, naming the components you are evaluating.

Next steps

Evaluate Wargaming & Simulation Sandbox

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Wargaming & Simulation Sandbox guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Wargaming & Simulation Sandbox support guide.

Related products