Maps that never leave your deployment

Plexara serves everything a map needs from your own deployment: the map library, the styles in light and dark, the label fonts, the US state and county boundaries, and a street map of the regions your team chooses. A map your agent builds is an ordinary asset, a page in the portal with versions, sharing, comments, and a thumbnail, and every one of those surfaces draws the map from the same place.

Your admins choose the regions in the portal under Admin settings: the contiguous United States, Alaska, Hawaii, Puerto Rico, Canada, Mexico, the United Kingdom and Ireland, Europe, Australia, or a custom area. The settings page states a region's exact size before it is saved and shows its progress while it is prepared. The full contiguous United States, down to street level, is 8.8 GB and was ready on the demo deployment in about forty minutes.

Maps by state or county need no street map at all. The boundaries ship with the map library, so the most common business map, a value per state or per county, works the day the deployment does.

Every map in this piece was built by an agent in one working session against the ACME demo deployment, from data the platform already holds. The agent reads a built-in knowledge page that tells it how maps are made on this deployment and which regions it serves, so it does not draw a street map nobody can see, and it does not reach for a public map service.

The map pages carry no data of their own. Store locations and revenue live in one data file the maps read by reference, and the shared styles and map helpers live in two more. Replace the data file and every map built on it shows the new numbers the next time it opens, with nothing re-saved. A scheduled automation can keep that file current, which turns a one-off map into a live one.

Because the map is a real page and not a picture, it can do what a page can: tilt into 3D, circle a city, fly to a store when its name is clicked, or play back a history.

A replay is the map form of a timeline. The agent sorts the records by date and adds them to the map one at a time, with a running date and counts beside it. It reads faster than a table of opening dates and shows something a table hides: where the network grew first, and where it filled in later.

The strongest maps put your data next to data you do not own. Plexara reaches public and partner APIs through the same governed gateway it uses for everything else, so the agent can pull an outside source and the map can join it to your own records in the same page.

The weather-exposure map pulls the National Weather Service's active alerts, which name every county they cover, and checks each store against them. On the morning it was captured, 27 of 303 stores sat in a county under an active alert, among them a run of Southern California stores under a fire weather watch. The list beside the map says which alert and when it ends: an operations view that needs no weather vendor and no map vendor.

The county screen pulls Census population and median household income for every county and checks which counties already have a store. Forty-three percent of people in the contiguous United States live in a county with an ACME store. The largest county without one is San Diego, at 3.28 million people and a median household income of $102,000. A site-selection analyst would start there.

Hosted map services bill by the view. Mapbox counts a map load every time its library starts on a page and charges $5.00 per thousand after the first 50,000 a month. Google Maps charges $7.00 per thousand after the first 10,000. Free tiers cover light use. A map dashboard that 2,000 people open twice a working day is about 88,000 loads a month, past both free tiers before anyone shares it outside the company.

On Plexara a map view costs nothing beyond the deployment you already run. There is no per-view meter, no API key to provision, rotate, or leak, and no vendor account to add to the stack. The street map is storage in your deployment, sized before your admins save it.

Opening a map, following a share link to it, drawing its thumbnail, and exporting it to PDF send no request to a third party. The areas your people view, the places your data marks, and the fact that anyone looked at all stay in your deployment. The only request that ever leaves is the one that prepares a region's street map, made once when an admin saves it.

That also means a map works on a network that reaches nothing but your deployment. A map in a sensitive report, a deck presented in a locked-down room, or a share link opened from a restricted network draws the same streets as anywhere else.

A public media organization was building maps within days of the feature shipping. Its team asked for a presentation of its community events and donors: a fly-in across Southern California to every event venue, a guided tour that flies from venue to venue with that event's photo, attendance drawn as 3D columns, a replay of a year and a half of events, and donors shaded by county and by state. The deck presents live in the portal, and every map in it draws from the organization's own deployment.

Ask for the map in plain language and say where it should go: "Make a map of our stores sized by last year's revenue and save it to Plexara." Naming Plexara matters, because an assistant left to itself tends to build a file on your own machine, where nobody else can open it and the deployment's street map does not reach. Saved to Plexara, the map is a page your team can open, share, comment on, and export.

From there, ask for what the question needs: "show it in 3D", "replay it by opening date", "shade the counties by median income", or "mark every store under a weather alert today".