Platforms on visible map layers, including those outside the current view. Select a name or row to focus its marker.
Name / platform
Type
Country
Deployment
Actions
Guide
How MISSILES Works
DISCLAIMER: The information provided in this application is for scientific, educational, and experimental purposes only.
While we strive to present accurate and useful data, the information contained herein may not be verified or completely reliable.
We do not promote, condone, or encourage warfare, violence, or aggressive actions of any kind. This application is intended solely
for research and educational exploration, and users are advised to exercise caution and responsibility when interpreting or utilizing the data presented.
MISSILES is a country-scale simulation platform for testing defense posture, optimizing attack plans, and evaluating outcome quality against cost. You can model launchers, air defenses, EW jammers, anti-drone doctrine, and synchronized target waves in one scenario.
1) Deploy Forces Across the Theater
Place offense launchers and layered defense systems on the map. You can deploy interceptor-based defenses, anti-drone gun systems, EW jammers, and location-based target areas, including country-level distributions.
2) Plan a Protected Area Automatically
Open Build → PROTECT AN AREA to draw a box or polygon, select allowed supplier countries and defense roles, enter a procurement budget, and set soft spending targets. The planner uses reviewed catalog capabilities to create a deterministic layered proposal without changing the current workspace.
3) Review and Deploy the Defense Preview
Review proposed systems, launcher counts, locations, costs, role spending, threat-specific coverage, EW effects, and defensive depth. Coverage values are planning estimates rather than interception guarantees. Deployment adds the plan to the current working map. After deployment, the named boundary remains visible and is included in normal deployment saves.
4) Build Attack Plans and Timing
Create targets manually or auto-generate them by country or custom area. Assign launch timing patterns, spread salvos, and test different strike packages to compare operational outcomes.
When saving or updating a deployment, keep Include targets enabled to store the current target positions, launcher assignments, and launch times. Loading the deployment restores those targets and remaps them to the restored launcher IDs. Turn the switch off only when you intentionally want a platform-only deployment.
5) Run the Simulation Engine
The engine calculates flight paths, detection and interception opportunities, anti-drone engagement priority, and EW jamming effects. This enables realistic comparisons across missile, drone, bomb, and artillery attacks.
6) Evaluate Decision Reports
Simulation reports provide launched, hit, intercepted, and jammed outcomes, plus success rate, total attack spend, and money burnt on ineffective attacks. This supports go/no-go decisions on whether a strike plan is worth executing.
DISCLAIMER: The information provided in this application is for scientific, educational, and experimental purposes only.
While we strive to present accurate and useful data, the information contained herein may not be verified or completely reliable.
We do not promote, condone, or encourage warfare, violence, or aggressive actions of any kind. This application is intended solely
for research and educational exploration, and users are advised to exercise caution and responsibility when interpreting or utilizing the data presented.
Attack optimization in MISSILES focuses on maximizing target effects while minimizing non-productive expenditure. You can compare multiple strike plans and select the one with the best operational and economic profile.
Launcher Allocation Strategy
Distribute targets across launchers to avoid overconcentration. Balance long-range assets and specialized ammo types to maintain sustained pressure and improve hit probability across the wave.
Timing and Saturation Control
Adjust launch timing to test synchronized arrival versus staggered waves. This helps identify the point where defense layers are stressed and where additional shots become diminishing returns.
Area-Based Target Generation
Use country, box, or polygon area selection to model campaign-scale target sets. This supports realistic attack planning beyond single-point engagements.
Cost-Effectiveness Decision Loop
Use simulation reports to compare success rate, total cost, and money burnt. If additional salvos increase spend without increasing effect, you can reject that plan before execution.
DISCLAIMER: The information provided in this application is for scientific, educational, and experimental purposes only.
While we strive to present accurate and useful data, the information contained herein may not be verified or completely reliable.
We do not promote, condone, or encourage warfare, violence, or aggressive actions of any kind. This application is intended solely
for research and educational exploration, and users are advised to exercise caution and responsibility when interpreting or utilizing the data presented.
Simulation reports translate scenario outcomes into measurable decision signals. They help planners answer one core question: does this attack profile produce enough effect to justify its cost?
Outcome Metrics
Core outcome metrics include launched, hit, intercepted, and jammed. Combined with success rate, they show whether a plan is operationally effective against the modeled defense posture.
Ammo-Type Breakdown
Reports separate missiles, drones, artillery, and bombs. For each type, you can compare launched volume, achieved hits, defensive disruption, and remaining inefficiency.
Cost and Money Burnt
Total cost shows attack spend. Money burnt reflects expenditure that did not result in successful hits. This is the fastest indicator of waste in a scenario.
Attack Worthiness Assessment
A plan may produce tactical hits while still failing financially. Use success and spend together: a high burn-to-hit ratio signals poor strategy and supports rejection or redesign.
Planner Coverage vs. Simulation Outcomes
Area Defense Planner coverage is a geographic planning estimate. It does not predict interception success. Deploy the proposed defenses and run a simulation to measure actual modeled detections, interceptions, jams, ammunition use, and cost outcomes.
DISCLAIMER: The information provided in this application is for scientific, educational, and experimental purposes only.
While we strive to present accurate and useful data, the information contained herein may not be verified or completely reliable.
We do not promote, condone, or encourage warfare, violence, or aggressive actions of any kind. This application is intended solely
for research and educational exploration, and users are advised to exercise caution and responsibility when interpreting or utilizing the data presented.
MISSILES supports planning workflows where geography, saturation, and layered defense interactions matter. These use cases help teams evaluate effectiveness and cost before committing operations.
National Air Defense Stress Testing
Model country-wide defense layouts, then run mixed incoming threats to locate weak sectors, delayed response zones, and overcommitted interceptors.
Budget-Constrained Area Defense Planning
Draw a region that may cross borders, restrict procurement to explicitly approved suppliers, and balance Anti-air, Anti-drone, and Jammer spending. Compare the generated planning preview before replacing the current workspace.
Coordinated Strike Feasibility
Simulate multi-axis launches with synchronized arrival times. Compare competing plans to identify which one delivers required effects with lower attack spend.
Anti-Drone Doctrine Validation
Evaluate anti-drone-first behavior against drone-heavy waves. Measure when gun-first doctrine reduces expensive interceptor usage and improves campaign cost profile.
EW and Counter-EW Planning
Test jammer coverage and probability effects against drone and missile threats. Validate whether EW investment changes mission outcomes enough to justify deployment cost.
Go or No-Go Decision Support
Use report metrics, especially success rate and money burnt, to determine if an operation is economically and operationally viable.
DISCLAIMER: The information provided in this application is for scientific, educational, and experimental purposes only.
While we strive to present accurate and useful data, the information contained herein may not be verified or completely reliable.
We do not promote, condone, or encourage warfare, violence, or aggressive actions of any kind. This application is intended solely
for research and educational exploration, and users are advised to exercise caution and responsibility when interpreting or utilizing the data presented.
MISSILES includes electronic warfare jamming as a dedicated defense layer. EW systems can disrupt incoming threats and change both tactical outcomes and cost curves in country-scale scenarios.
What EW Changes in the Simulation
When a target enters jammer range, jamming probability is evaluated per engagement. Successful jamming is treated as a mission kill for that threat, altering downstream interception demand.
Drone and Missile Behavior
Drone and missile interactions are modeled differently, allowing planners to test realistic doctrine tradeoffs. EW can reduce pressure on interceptor inventories when placed effectively.
Operational Planning Impact
By comparing scenarios with and without EW, teams can measure if jammer investment reduces money burnt and increases campaign efficiency.
Effect-Aware Area Defense Planning
The Area Defense Planner keeps GNSS, datalink, communications, radar, and drone-related EW coverage separate. A jammer receives planning credit only for reviewed effects it supports, preventing a large EW circle from being presented as universal protection.
DISCLAIMER: The information provided in this application is for scientific, educational, and experimental purposes only.
While we strive to present accurate and useful data, the information contained herein may not be verified or completely reliable.
We do not promote, condone, or encourage warfare, violence, or aggressive actions of any kind. This application is intended solely
for research and educational exploration, and users are advised to exercise caution and responsibility when interpreting or utilizing the data presented.
MISSILES models anti-drone doctrine with engagement sequencing that prioritizes anti-drone systems first. This allows realistic testing of low-cost interception before expensive anti-air interceptor release.
Path-Based Engagement Priority
When anti-drone-first mode is active, the first anti-drone platform along the drone path engages first. Other systems engage only after the drone exits the first platform engagement window.
Layered Defense Efficiency
Gun-first doctrine can preserve anti-air interceptor inventory for non-drone threats. Use scenario comparisons to measure inventory efficiency and mission resilience.
Planning Anti-Drone Coverage for an Area
The Area Defense Planner can assign procurement spending to the Anti-drone role while retaining every selected system's real capabilities. It uses reviewed drone-interception and anti-drone gun ranges rather than unrelated maximum ranges, and multifunction systems are purchased only once.
Cost-Aware Doctrine Validation
Simulation reports quantify hit, intercepted, and jammed outcomes with spend metrics, so planners can test whether anti-drone doctrine lowers money burnt and improves net effect.
DISCLAIMER: The information provided in this application is for scientific, educational, and experimental purposes only.
While we strive to present accurate and useful data, the information contained herein may not be verified or completely reliable.
We do not promote, condone, or encourage warfare, violence, or aggressive actions of any kind. This application is intended solely
for research and educational exploration, and users are advised to exercise caution and responsibility when interpreting or utilizing the data presented.
PROTECT AN AREA creates a deterministic, budget-constrained defense proposal for a user-drawn region. The protected area is only a label and polygon: it is not resolved to a country, and no domestic supplier is added automatically.
Planner Workflow
Open Build → PROTECT AN AREA.
Enter an area name and draw either a box or free polygon on the map.
Select every supplier country the planner is allowed to use.
Select Anti-air, Anti-drone, Jammers, or all three roles.
Enter the total procurement budget in millions of USD.
Adjust the role sliders. They automatically rebalance to exactly 100%.
Choose Generate Preview, inspect the proposal, then use Back / Edit or Deploy Plan.
Suppliers and Catalog Availability
Every supplier must be selected explicitly. The supplier list contains only countries represented by reviewed defense platforms in the current catalog. Joint systems are eligible when either participating supplier is selected. For example, a France-Italy system may be considered when France or Italy is allowed.
Defense Roles and Real Capabilities
Anti-air remains threat-aware across aircraft, cruise missiles, ballistic missiles, hypersonic threats, bombs, artillery, and other missiles. Anti-drone uses reviewed drone-interception or counter-UAV gun capabilities. EW coverage remains separate for GNSS, datalink, communications, radar, and drone-related effects.
A multifunction system has one assigned spending role but keeps all of its reviewed capabilities in the coverage analysis. It is purchased and charged only once.
Budget and Allocation
Role percentages are soft spending targets. The planner must remain within the total budget and represent every selected role, but it may deviate from the requested split to produce a useful plan. After broad coverage and capability diversity, it adds meaningful capacity and resilience toward at least 90% budget utilization when the selected catalog supports it. Preview explains when catalog limits or remaining funds prevent further useful purchases.
How Locations Are Chosen
The planner combines uniform land points with weighted cities, security and military-related sites, military transport infrastructure, and civilian transport infrastructure. Population weighting is capped so one large city cannot dominate the whole plan.
It first seeks new weighted geographic coverage, then improves capability and layer diversity, and finally adds launcher depth at important locations when new placements offer little additional coverage.
Understanding the Preview
The preview shows temporary markers and capability-specific range layers, requested and actual spending, selected systems, launcher counts, geographic and priority-site coverage, threat-class coverage, EW-effect coverage, and points protected by multiple sites. Preview generation does not alter platforms, defenses, camps, targets, or saved deployments.
Important: coverage is a planning estimate, not a guarantee of detection or interception. Run the simulation after deployment to evaluate modeled operational outcomes.
Deploying the Plan
Deployment requires explicit confirmation. The server independently revalidates the polygon, suppliers, roles, templates, launcher limits, coordinates, and authoritative costs before making changes. A successful deployment adds the new area and defenses to the current workspace; existing platforms, defenses, camps, targets, and protected areas remain.
The insertion is atomic: if validation or insertion fails, the transaction rolls back and the existing workspace remains intact. A loaded deployment remains linked and is marked modified so Update Loaded can save the addition.
Saved Boundaries and Moving Defenses
The named protected-area boundary is saved automatically with the active workspace. Signed-in users keep it under their Google account; guests keep it for their current browser session. The purple boundary is visible by default and can be shown or hidden from Layers → Protected areas.
Layers → Protected areas lists every area with its current linked count, outside count, and authoritative procurement spend. There is no application limit on how many areas may be added, including overlapping areas. Hovering the map label shows current spend; use Zoom or Details to inspect an area, Edit to rename or redraw that specific area, Delete to remove its boundary, or Protect another area to keep building the workspace.
Select the boundary to review current procurement spend, geographic, priority-site, capability, and layer-depth estimates. Moving, editing, or deleting a linked defense refreshes these estimates. A boundary does not automatically move with its defenses, but its name and polygon can be edited at any time. A linked system outside it is clearly identified and still contributes wherever its reviewed range reaches planning points inside the area.
When manually placed air defenses are inside a boundary, Update Area appears. It adds those systems without removing prior links. A defense may support multiple overlapping protected areas.
Deleting a protected area removes only that area and its defense relationships. The linked defense platforms remain in the workspace and may be attached to another area later.
Normal deployment Save and Update operations include protected areas. Loading, combining, copying, or sharing a deployment restores the named boundaries and their links to generated defenses.
Browse offense and defense systems. Select a platform for its overview, navigation, capabilities and simulation specifications.
Simulation Controls
8000 m
Simulation Controls
Simulation Speedx100
8000 m
Anti-drone doctrine: drones are engaged by anti-drone guns first. Interceptor missiles are released when no viable gun engagement exists or when remaining drone-to-target distance is at/below urgent distance. Enable poor drone detection to simulate reduced air-defense detection reliability against drones. Point-defense-first missile doctrine prioritizes shorter-range systems for missile interceptions when enabled.
Simulation speed: x100
Add/Edit an Offense Platform
Delete Offense Platform
Are you sure you want to delete this platform;
Delete Defense Platform
Are you sure you want to delete this platform?;
Select firing launcher
Auto-generate targets
A platform is eligible when it can reach the selected country or area.
Only systems from explicitly selected suppliers will be considered.
3 Defense roles
4 Budget
$
million
5 Allocation
These are soft targets and always total 100%.
6 Availability
Choose suppliers and roles to check availability.
Preparing planning points…0%
PLANNING ESTIMATE
PREVIEW
System
Supplier
Assigned role
Actual capabilities
Relevant range
Launchers
Location
Cost
Coverage values are geographic planning estimates, not guarantees of interception success.
Simulation Report
PROTECTED AREA
Protected area
EDIT PROTECTED AREA
Edit area
The existing boundary will remain unless you redraw it.
Delete Protected Area
Delete this protected area?
Its boundary and defense links will be removed. Linked defense platforms will remain in the workspace.
About the simulator
DISCLAIMER: The information provided in this application is for scientific, educational, and experimental purposes only.
While we strive to present accurate and useful data, the information contained herein may not be verified or completely reliable.
We do not promote, condone, or encourage warfare, violence, or aggressive actions of any kind. This application is intended solely
for research and educational exploration, and users are advised to exercise caution and responsibility when interpreting or utilizing the data presented.
Country-Scale Defense Simulation and Attack Optimization
MISSILES is built for whole-country scenario modeling: deploy layered air defense networks, run coordinated attack plans,
and optimize strike timing and platform usage before committing to a strategy.
Every simulation report provides decision metrics including launched, hit, intercepted, and jammed outcomes,
plus success rates, total attack spend, and money burnt on ineffective attacks so you can evaluate whether an attack is worth it.
Country Coverage Simulate full-country defense and offense scenarios.Read how it works
Attack Optimization Tune launch patterns, timing, and target allocation.Explore optimization
Decision Reports Compare operational success against attack and defense costs.See report guide
Yes. You can deploy offense and defense platforms at country scale and run synchronized simulations across the full map.
Does the platform support attack optimization?
Yes. You can optimize launcher assignment, timing, and target generation to test alternative strike plans and compare outcomes.
Can I measure if an attack is worth executing?
Yes. The report includes success rates and cost metrics like total spend and money burnt to support go/no-go decisions.
Select Action
What would you like to add?
Add/Edit Air Defense System
Add/Edit Camp
Delete Camp
Are you sure you want to delete this camp?
Instructions & Simulation Logic
Build scenarios, explore platform capabilities, and compare simulated outcomes. Results use configured estimates and are not predictions of real-world performance.
Quick start
Deploy. Choose Offense or Air defense.
Add platforms and targets. Place platforms, select templates and add targets through Deploy.
Simulation. Set preferences and select Simulate! or Run.
Inspect the report. Compare outcomes and costs, adjust and run again.
Platforms and profiles
Open Deploy → Offense or Air defense, choose a location, select a template, name the platform and save. Select a map marker to inspect or edit it; drag it to reposition.
For air defense, set Launchers to deploy within the template limit. The form shows interceptors per launcher and the total available.
Enable Keep adding to place more copies with the same settings. Tap or click successive map locations; select Done or press Escape to finish.
Use View Info to inspect the model, country flag, specifications and capabilities. Green ticks mean enabled; red crosses mean disabled. Disabled Anti-drone gun and EW jammer sections show only their Enabled status.
Select the profile image to enlarge it. Close the viewer with its X, Escape or a click outside. Available image credits are shown in the viewer.
Copy link copies the public platform profile and changes to a tick and Copied!. The permalink opens that reference page separately; it does not include your map scenario.
Protected areas
Open Deploy → PROTECT AN AREA, name the area and draw a box or polygon. Select supplier countries, defense roles, a procurement budget and role allocations.
Choose Generate Preview to review the proposal before Deploy Plan adds it to the current workspace. Coverage is a geographic planning estimate, not a guarantee of interception.
Manage independent or overlapping areas through Layers → Protected areas. Area labels show current spend on hover.
Edit renames or redraws an area. Delete removes its boundary without deleting linked defenses. Manually placed defenses inside a boundary enable Update Area.
Targets and map controls
Use Deploy → Target, choose a map location and select an eligible launcher. Use Auto Targets for country- or area-based generation, launcher balancing and launch-delay options.
Drag target markers to reposition them. With a mouse, right-click the map to create a target or right-click an existing target to remove it.
Use Layers to choose a base map, toggle visible layers and range rings, and find protected areas. The Targets, Blasts, Offense and Defense shortcuts toggle map overlays; they do not remove platforms.
Use the map zoom controls for precise placement. Clear removes the current map setup after confirmation; save a deployment first if you want to keep it.
Running simulations
Open Simulation to set animation, rocket icons and simulation speed. Select Simulate! or the Run shortcut to run the current scenario.
Prefer anti-drone first conserves interceptor missiles while a viable gun engagement exists. Missile fallback becomes available when no viable gun engagement remains or the drone reaches the configured urgent distance from its final target.
Prefer point-defense first (missiles) gives available shorter-range defenses priority against missile targets. Longer-range systems remain a fallback when shorter-range candidates cannot engage or have no ammunition.
Randomized probabilities mean repeated runs can produce different outcomes. Compare results as simulation estimates rather than guaranteed performance.
Detection, interception and EW
Eligibility: interceptor and gun engagements require a supported target class and a viable detection and engagement opportunity. Range, reaction time, reload intervals, speed and simultaneous-target capacity constrain attempts.
Interceptor missiles: each attempt consumes finite interceptor ammunition. Success depends on configured accuracy, target speed, tracking load and randomized modifiers.
Anti-drone guns: guns require enabled capability and remaining ammunition. Each attempt uses one bullet per 100 metres of engagement distance, rounded up with a minimum of one; expenditure uses the configured per-bullet cost.
EW jammers: the jammer must be enabled, in range and compatible with the target’s drone-control, GNSS, datalink, communications or radar dependencies. The yellow ring indicates EW range.
A successful jam neutralizes the target before impact. EW resistance, autonomous navigation and inertial backup reduce relevant jamming probabilities without granting automatic immunity.
Saving, sharing and reports
Sign in with Google to save and load deployments through Saved. Save the current workspace, load one or more deployments, or update an existing deployment.
Keep Include targets enabled when saving or updating to preserve target positions, launcher assignments and launch times. Disable it for a platform-only deployment.
Use Saved → Share deployment to share a saved map setup. Copy Link follows future updates; Copy Once freezes the current saved state. Save your changes first.
A platform profile link shares only the catalog entry, not your placements, targets or saved deployment. The general Share action shares the current page URL; it does not save unsaved map changes.
Read live totals and the final report for launched threats, hits, interceptions and jams. Review success rates, offensive expenditure and defense costs together.
Reports include EW attempts, successes, failures and spend by defense system. Money burnt represents offensive spend on threats that did not hit; it is not a measure of real-world damage or loss.
Limitations and disclaimer
Catalog specifications, cost estimates and modeled capabilities may be incomplete or simplified. Image sources identify the pictured platform; they do not validate simulation values.
DISCLAIMER: The information provided in this application is for scientific, educational, and experimental purposes only.
While we strive to present accurate and useful data, the information contained herein may not be verified or completely reliable.
We do not promote, condone, or encourage warfare, violence, or aggressive actions of any kind. This application is intended solely
for research and educational exploration, and users are advised to exercise caution and responsibility when interpreting or utilizing the data presented.