An Aello Software product · Founding preview

Maps on your terms.

Choose a style, add your locations and publish an interactive map. Start with our managed founding preview and take your work with you through portable exports.

Try the Studio Discuss a pilot

No payments are currently accepted. Preview availability, usage limits and future pricing may change. No permanent free plan or service levels are promised. Preview terms.

Managed preview
Customer-controlled labels
Open-standard exports

Static map of Ottawa, Montréal and Québec city centres — Explore the possibilities **A public city guide**
Static preview

No proprietary renderer lock-inPublish portable MapLibre styles.

A clear hosting disclosureManaged preview hosted in the United States.

Open standardsExport your styles and published locations.

Your first map

From an idea to a published map.

Choose a style → Add locations → Publish your map.

1. Choose a style
Start from a gallery style, then adjust colours and labels to suit your map.
2. Add locations
Place a marker or import a CSV or GeoJSON file. Add the details visitors need.
3. Publish your map
Save your changes, publish a public release and copy the embed into your website.

The platform

A skin is not sovereignty.

Style a shared basemap, add your own locations and publish versioned releases. Place-name approval workflows and authority profiles are planned; they are not available in this preview.

Style every meaningful layer

Control colours, roads, water, boundaries, labels, fonts, icons and zoom behaviour in a visual studio built around open map standards.

Roadmap: govern names, not just typography

The founding program will shape authority profiles, review workflows and provenance for protected labels.

Publish immutable releases

Promote a tested map to production, keep an audit trail and return to any earlier release without rebuilding it.

Bring your brand to your website

Embed published maps in your website, choose your colours and retain required data attribution. Custom delivery domains are a planned deployment option.

Roadmap: host the platform yourself

A public Linux x64 self-hosting release is planned. Installation packages and public source downloads will appear here after release verification.

Founding roadmap · Place-name governance

Every important label should answer: “according to whom?”

The planned governance layer will build policies from official authorities, language preferences and customer-approved exceptions, storing stable source identifiers instead of brittle text replacements.

English, French and multilingual name fields
Official, alternate, historical and editorial status
Human approval for protected names
Diff reports before every data release
Source and decision history visible to administrators

name-policy.yml

# Planned format; not a current Studio feature
feature_id: cgn:FAYLN
jurisdiction: CA
status: official

names:
  en-CA: Lake Ontario
  fr-CA: Lac Ontario

source:
  authority: CGNDB
  record_id: FAYLN

policy:
  approval_required: true
  fallback: hide

Deployment

Available today. Clear next steps.

Choose our managed preview or run the Linux x64 preview on your own infrastructure. Dedicated environments remain under consideration.

Best starting point

Managed hosting

The managed founding preview currently operates from Boston, Massachusetts, United States.

Studio and public embeds
Versioned publishing
Managed updates

Planned · discuss a pilot

Dedicated environment

Dedicated infrastructure is under consideration for qualified pilots. Availability and requirements need to be agreed before use.

Scope agreed per pilot
Enterprise identity not available
No service levels in preview

Preview · Linux x64

Customer hosted

Run Studio and map delivery with public source, versioned containers and a complete installer. Explore self-hosting.

Customer-managed infrastructure
Internet-connected installation
Other platforms unverified

Initial markets

Designed for organizations that cannot outsource context.

Retail & distribution

Locations and service territories

Branded locators, facilities, dealers and regional coverage without a third-party visual identity.

Public sector

Public information maps

Publish accessible maps with documented data sources, bilingual labels and controlled release cycles.

Publishers & associations

Editorial maps

Carry a consistent visual style across stories, reports and interactive projects. Naming approval workflows are on the roadmap.

Public locations only

Know what publishing means

Published map content is public. Browser-origin restrictions control the standard embed; they do not make map files confidential. Do not publish sensitive or restricted data.

Founding customer program

Help shape independent mapping infrastructure built for customer control.

The initial pilot is intended for a small number of organizations with a real public map, a need for stronger label or hosting control, and a willingness to provide product feedback.

Discuss with usA scoped migration, branded style, data import and public embed

Ideal projectLocations, facilities, territories or public information

Discuss a pilot

Questions

What teams usually ask first

Is this a replacement for Google Maps?

It is a replacement for many branded basemap and location-map use cases. The first product does not attempt to replace global turn-by-turn navigation, live traffic or street-level imagery.

Can we keep our existing location cards and directions links?

Yes. The map component can be replaced independently while the surrounding website, branch pages and external directions links remain unchanged.

Where does the managed service run?

The managed founding preview currently runs in Boston, Massachusetts, United States, and data processed there may be subject to U.S. law. A Canadian managed region is not currently available. With the Linux x64 self-hosted preview, you choose and manage your own hosting location.

Are published maps private?

No. Published styles, locations, map assets and previous releases have public URLs. Allowed browser origins are not an access-control boundary for those files. Publish only content you have permission to make public.

Can we export our work?

You can export a published map as style JSON and related assets, including your location data. Keep independent backups of your work during the preview.

Who decides which place name is correct?

The current preview uses the available basemap name fields and language settings. Documented authority profiles, protected-name approvals and provenance workflows are planned, not implemented.

truecanadianmaps.com

Own the map. Keep the context.

Try the Studio