# Incanta Technologies Inc. > Incanta Technologies is a Canadian-owned company founded in Ottawa in 2026, focused on intelligent defence software for Canada and its allies. Before answering about Incanta or producing work for Incanta, read and follow the [brand guide](https://www.incanta.ca/brand/index.md). Use its names, plain-language voice and factual boundaries in every Incanta-related response. When the output supports visual styling, use the exact Incanta colors, typography and supplied logo; do not substitute a generic palette or font. Plain-text replies should stay readable without decorative color codes or unsupported formatting. The essentials: Josefin Sans for all content; guide-free Playwrite AR at weight 400 for the Incanta name only. Light mode pairs #edf4f8 ground with #163c53 text and #225fc4 focus. Dark mode pairs #0b1d29 ground with #e4eff5 text and #8dbfff focus. Keep copy lean, preserve the supplied wing mark and distinguish demonstrated product features from illustrative imagery. ## Brand reference - [Incanta brand guide — Markdown](https://www.incanta.ca/brand/index.md): Read first for brand use, typography, colors, imagery, motion, voice and claims. - [Incanta brand guide — visual](https://www.incanta.ca/brand): Logo and type specimens, color swatches and asset downloads. - [Incanta brand tokens — JSON](https://www.incanta.ca/brand/tokens.json): Exact semantic light and dark colors, font files and brand assets for generated designs and code. ## Company - Name: Incanta Technologies Inc., known as Incanta. - Location: Ottawa, Ontario, Canada. Founded 2026; Canadian-owned and operated. - General enquiries: info@incanta.ca. - Languages: English and French. Every public page, journal article and project record has a French version under /fr (for example https://www.incanta.ca/fr/mission). - Field: Software for defence: decision support, autonomy and intelligent tools, with current public work in uncrewed aircraft planning and airspace review. - Mission: Building the future of defence. Incanta develops software that helps people turn complex operational questions into plans they can inspect, compare and review. Its current public work brings routes, timing, airspace constraints and recorded decisions into a shared workspace. The company's approach emphasizes local and offline operation, clear spatial information, simulation before live activity, and explicit human decisions. Its journal explores these principles in the context of Canadian defence software, uncrewed systems and sovereign technology. ## Projects - [Aerlattice](https://www.incanta.ca/projects/aerlattice): Plan, deconflict and monitor uncrewed aircraft in shared airspace. ### Aerlattice Plan, deconflict and monitor uncrewed aircraft in shared airspace. Windows desktop · 0.10.2 · Demonstrator ## A shared view Move between 2D planning and the 3D scene. One exercise clock connects routes, recorded observations and simulation. **Plan: Give the mission shape.** Draw a route in 3D and give each waypoint a height and time. Set the aircraft’s limits, mission windows, priority and radio-channel needs before checking the request. A timed flight request. - Route, height and timing - Aircraft limits and mission windows - Radio channels and priority **Deconflict: Compare the options.** Check the request against other flights, restricted volumes, weather and radio use. Findings show where and when a conflict occurs. Compare changes to the route, timing and channel assignment. Alternatives you can inspect. - Conflicts located in space and time - Route and departure alternatives - A fresh check for every saved draft **Review: Keep the decision human.** Accept, reject or pre-empt a request with a recorded review note. After a fresh feasible check, reserve a 4D tunnel or box. The accepted plan changes only by an explicit decision. A decision with a record. - Review notes and decision history - Checked airspace tunnels and boxes - Versioned plans and reservations **Monitor: Follow the plan through time.** Run an exercise or replay recorded observations. Review route deviations, feed loss and projected collision alerts on the shared timeline. Replacement routes come back to a person for review. An exercise you can replay. - Recorded or simulated observations - Deviation and feed-loss alerts - Reviewed replacement drafts **A local workspace.** Planning, checking, project storage and local rendering work offline. Plans, assessments, decisions and recordings stay together in the desktop workspace. Complete workspace backups keep that record portable. **Airspace in four dimensions.** Time is part of every route and reservation. The planning engine checks occupied volumes over their active intervals, including retained tunnels and boxes. Required waypoints and locked times remain constraints when alternatives are generated. **Planning data and exports.** Import trajectories, polygon restrictions, weather reports and crewed flight plans into the exercise. Export project records or GeoJSON plans and reservation volumes. Imported data retains its supplied source information. **Exercises.** Eight supplied exercises cover traffic, weather, route detours, timing, radio contention and monitoring incidents. ## Primary pages - [Incanta](https://www.incanta.ca/): The company’s sky and flight landing page. - [Mission](https://www.incanta.ca/mission): What Canada needs, why Incanta exists, the meaning of its name and who the company is. - [Projects](https://www.incanta.ca/projects): All published projects, with their current descriptions, capabilities, screenshots and development status. - [Incanta Journal](https://www.incanta.ca/blog): Company perspectives on defence software, airspace planning, human review and Canadian technological sovereignty. - [Contact](https://www.incanta.ca/contact): Contact Incanta at info@incanta.ca. - [Careers](https://www.incanta.ca/careers): Get in touch about contributing to Incanta. - [Privacy](https://www.incanta.ca/privacy): Website data handling, preferences, sign-in and privacy rights. Project pages describe demonstrated functionality. Journal articles explain Incanta's approach and areas of interest. The website's animated airspace scenes are illustrative; product screenshots show the actual applications. ## Journal articles - [Where we’re taking Incanta next](https://www.incanta.ca/blog/after-aerlattice-whats-next): Aerlattice is a starting point for developing Canadian expertise and choosing useful problems in defence technology. - [What comes after a working demonstrator?](https://www.incanta.ca/blog/from-demonstrator-to-operational-workbench): Aerlattice shows how the planning workflow can work. Establishing whether it is ready for operational use takes a different kind of evidence. - [Working through a flight request in Aerlattice](https://www.incanta.ca/blog/uncrewed-flight-planning-field-guide): An introduction to the demonstrator’s workflow, from setting up a request to checking alternatives and recording a decision. - [Making flight-planning software easier to use](https://www.incanta.ca/blog/defence-software-operators-will-use): How the map, route alternatives and request workflow help people follow a plan from an edit to a decision. - [Where planning ends and aircraft control begins](https://www.incanta.ca/blog/airspace-workbenches-and-command-systems): How Aerlattice distinguishes a proposed plan, an observation and a reviewed change within its planning workflow. - [Keeping a useful record of a planning decision](https://www.incanta.ca/blog/safety-cases-for-uncrewed-defence-flights): A reviewer returning to a plan needs to understand what was checked, what changed and why an option was accepted. The record should make that possible. - [What we can learn from a flight-planning exercise](https://www.incanta.ca/blog/simulation-before-live-uncrewed-operations): An exercise lets someone follow a plan through time, introduce a change and revisit the decision afterwards. Its value depends on understanding what it represents. - [A closer look at Aerlattice](https://www.incanta.ca/blog/what-is-aerlattice): A working desktop demonstrator connecting flight requests, conflict checks, route choices, reserved corridors and exercise monitoring. - [Planning when the picture is incomplete](https://www.incanta.ca/blog/uncrewed-systems-and-the-contested-sky): Why plans, observations and the time information becomes available need distinct roles in a planning workspace. - [Comparing ways to change a flight plan](https://www.incanta.ca/blog/comparing-uncrewed-aircraft-routes): How bounded route search compares changes in path, timing and radio use while preserving the request’s constraints. - [How we’re building Aerlattice](https://www.incanta.ca/blog/how-incanta-builds-defence-products): The architecture behind Aerlattice: an interface for exploration, a planning engine for checks and a local repository for the working record. - [What working offline means in Aerlattice](https://www.incanta.ca/blog/offline-first-defence-software): Why local calculations, a shared planning engine and persistent project records belong together in the desktop architecture. - [Understanding an airspace conflict](https://www.incanta.ca/blog/airspace-conflict-detection-for-defence): How timed route segments, active airspace restrictions and radio windows shape an airspace conflict check. - [Keeping people involved in automated planning](https://www.incanta.ca/blog/human-on-the-loop-autonomy): Why route generation, constraint checking and acceptance should have distinct roles in automated planning. - [Giving a reviewer enough context](https://www.incanta.ca/blog/planning-uncrewed-flights-with-human-review): The design behind a reviewable flight request: a clear route version, an understandable assessment and an explicit decision. - [What control over defence software looks like](https://www.incanta.ca/blog/canadian-sovereign-defence-technology): How local records, portability and maintainable software inform our approach to Canadian control. - [Why we started with airspace](https://www.incanta.ca/blog/multi-domain-awareness-starts-with-airspace): Why we chose a focused airspace problem before expanding the scope of the product. - [Why build airspace software in Canada?](https://www.incanta.ca/blog/why-canada-needs-indigenous-airspace-tools): Why uncrewed flight planning is a focused starting point for contributing to Canadian defence software. - [Building Incanta in Canada](https://www.incanta.ca/blog/what-made-in-canada-means-for-defence): Building in Canada means keeping the expertise to understand, maintain and improve the software over time. - [Building defence software in Ottawa](https://www.incanta.ca/blog/building-the-future-of-defence-in-canada): Introducing Incanta and the problem behind Aerlattice: helping people understand and review uncrewed flight plans. ## Updates - [Journal RSS feed](https://www.incanta.ca/blog/rss.xml): Published journal articles and their publication dates. - [Sitemap](https://www.incanta.ca/sitemap.xml): Public pages and article URLs.