See the whole community. Act on what matters.
Mapsys connects community knowledge, emergency response, buildings, infrastructure, operations, planning and history through place. Everything below is a real capture from the product — or an open statement that the capture doesn't exist yet.
Communities don't lack information. They lack a system that connects it.
Housing lives in one spreadsheet. Infrastructure lives in a consultant's drawing set. Family information lives in someone's memory. Emergency contacts live in a binder. Each one is accurate. None of them know about each other.
During normal operations that fragmentation costs time, repeated work, missed maintenance and lost history. During an evacuation it costs the thing you cannot rebuild in the moment: a shared picture of where people are.
The system used during a crisis should not disappear when the crisis ends.
Select anything. The record is already attached.
There is no separate asset database to reconcile. A service line, a building, a road, a family, a work order and a decision are all understood as places — so selecting one gives you its purpose, its ownership, its accessibility and its emergency role at the same moment.
- Purpose — why this place exists
- Ownership — who is responsible for it
- Accessibility — how people actually reach it
- Emergency role — what it becomes during a response
Type a name. Get the place — and everything serving it.
Mapsys search returns places, connections and actions. Never pages, never settings. Searching one building also surfaces the water service and the hydro service feeding it, because in Mapsys those are neighbours in the same record set.
Two networks. One community. One map.
Public works usually holds water in one system and hydro in another, drawn by different people at different times. Mapsys draws them together, in the road, at the same scale — so a shutdown, a service call or a new build is understood against everything else in the ground.
Follow the service from the road into the building it feeds.
The main in the road and the room on the far side of the wall are the same story. Following it end to end is what turns infrastructure data into an answer.
The routes shown are demo-authored on the Cedar Bend showcase community — a working continuity demonstration, not a certified utility as-built.
A building should be able to explain itself.
One building, one connected record: why it exists, the spaces inside it, the systems that serve it, the work done to it and the work it still needs. Not a dot on a map, a row in a spreadsheet and a folder somewhere else.
What is shown is the building opened into rooms and systems with its own condition and reason for attention. Full engineering-grade electrical documentation is not claimed.
Understand a building before the finished drawings arrive.
Create is the building design studio: enter, move, purpose. Start from intent, from a template, from a capture of a building that already exists, or from an imported model — then edit walls, rooms and fixtures immediately.
A community that can describe what it needs — in space, not adjectives — works differently with architects, engineers, funders and consultants. The conversation starts from something real.
Library knowledge suggests entrances, circulation, spaces and missing evidence. What you build in Create becomes the building record the community keeps afterwards.
- 01Bubble plan
- 02Walls appear
- 03Doors snap in
- 04Building completes
- 05In the community
Step 01
Start from what a space is for.
Scroll to follow the transformation
Diagram, not a product screenshot. It explains the sequence from intent to a building on the community map. Placement is proved by the capture above through the supported placement action — a pointer-drag recording is still owed.
When an evacuation starts, the coordination shouldn't.
An evacuation is not the moment to assemble a system. Because people, homes, hosts, accommodations and conditions already live in the same place, emergency mode is a change of view — not a change of software.
- People and families
- Movement and hosts
- Accommodations
- Support and contacts
- Changing conditions
- Return planning
The people who know the land should be the ones recording it.
Community members and field staff carry knowledge that never reaches an office system: a washed-out crossing, a hazard, a place that matters. My Mapsys is the personal surface where that knowledge is captured by the person who holds it, attached to the place it belongs to.
The capture shown is an emulated Android viewport with simulated location. It proves the interface, not physical field use — and offline basemap tiles are not claimed at all.
One record the community recognises as its own.
An observation is submitted by someone who was there, reviewed by someone accountable, and accepted into the record — or not. What the community accepts becomes the version everyone works from, including the next council and the next staff member.
Supporting a community should not require taking control of its information.
Submission, review and acceptance are captured. Publishing an accepted observation into Community Truth is not shown yet, so it is not claimed as finished.
Six systems that usually live apart — joined through one place.
Emergency, operations, buildings, Create, support and continuity are normally separate tools that never speak to one another. In Mapsys they write to the same map, the same records and the same shared memory, so work done for one need strengthens the next.
Diagram, not a product screenshot — it explains the relationship, not the interface.
Understand what needs attention — without asking six people first.
Leadership is usually expected to decide using information divided across departments, meetings, reports, consultants and personal conversations. Attention puts the signals already known for the community next to the map they happened on.
- Current community priorities and emergency conditions
- Housing, infrastructure and work requiring attention
- Community plans and capital projects
- Decisions, responsibilities and progress over time
What is captured today, and what we still owe you.
Every claim on this page is either backed by a capture above or listed here as outstanding. Nothing on this site is a rendered mock-up of Mapsys.
- See the whole community on one mapCaptured
- Understand any place from the mapCaptured
- Find what matters in one searchCaptured
- Water and hydro drawn togetherCaptured
- Follow a service from the road into a buildingPartly captured
- Buildings that explain themselves, room by roomCaptured
- Start a building from intent in CreatePartly captured
- Place a Library definition on the community mapPartly captured
- Capture knowledge in the field (emulated device)Partly captured
- An observation submitted, reviewed and acceptedPartly captured
- Pointer-drag placement from the Living LibraryCapture in progress
- Coordinate an evacuation — people, hosts, movement, returnPartly captured
- Field capture on a physical deviceCapture in progress
- An accepted observation published to Community TruthCapture in progress
- Offline basemap tilesCapture in progress
Captures from preview.mapsys.ca · Cedar Bend showcase community · evidence completion pass, 2026-08-05
Become a Founding Mapsys Community
Help shape the future of community intelligence while receiving exclusive launch pricing.
As Mapsys prepares for broader deployment, we're inviting five communities to become our Founding Community Partners.
Rather than simply purchasing software, these communities will help influence the next generation of Mapsys while receiving direct support from our development team.
To recognize that commitment, each selected community will receive 66% off their first year, including implementation and setup.
Once all five positions are filled, Mapsys will return to standard pricing.
Industrial Communities
2 positionsLooking for communities connected to:
- Mining
- Forestry / logging
- Energy
- Transportation
- Major infrastructure
PurposeHelp validate industrial planning, infrastructure management, environmental monitoring, emergency coordination and asset intelligence.
Small Community
1 positionLooking for one smaller community interested in modernizing planning, operations, emergency preparedness and community management.
PurposeDemonstrate that Mapsys scales equally well for smaller communities.
Traditional Land Mapping
2 positionsLooking for communities interested in documenting and protecting:
- Traditional knowledge
- Trails
- Language
- Harvesting areas
- Cultural sites
- Stewardship
- Land use
PurposeHelp shape one of the most important long-term directions of Mapsys.
What You'll Receive
- 66% off your first year
- Implementation included
- Priority onboarding
- Direct access to the Mapsys development team
- Priority feature requests
- Regular planning sessions
- Early access to new capabilities
- Opportunity to influence future development
What We Ask From Pilot Communities
Pilot communities should be willing to:
- Meet with us periodically
- Share honest feedback
- Help us understand real workflows
- Collaborate as Mapsys evolves
- Allow approved screenshots and demonstrations of their Mapsys implementation to be used for marketing and educational purposes. No confidential or sensitive community information will ever be shared without explicit permission.
Community data always remains owned and controlled by the community. Participation in the pilot does not change data ownership or sovereignty.
Applications Are Limited
Only five communities will be selected for this launch program. Once the pilot is full, new implementations will move to standard pricing.
If your community is interested in helping shape the future of Mapsys, we'd love to talk.
The problems are already here. The system to connect them should be too.
Start with one community need — evacuation, housing, infrastructure, operations, planning, or buildings — and build lasting community capacity from there.