1. Architecture in brief
Roady is a Foundation app with personal and company tenancy. PostGIS holds the authoritative geometry, with portable GeoJSON kept in step for import and export. Core records include places, zones, geofence rules, routes and stops, tracks and track points, and check-ins. CloudWinks supplies the application runtime and Crux the shared identity. Other apps point at a place or zone; Roady does not call those apps.
2. Service boundary and intake
Places, zones, routes, tracks and check-ins are created through Roady services. A consumer links a business record with a calling-application and subject pointer, or caches a place or zone identifier without a cross-app foreign key. Map-provider calls run on the server through the shared mapping service, with keys resolved in KeyKook. Legacy saved-map tables remain archived behind read-only views.
3. Data handled
The model stores places, zone geometry and provenance, geofence rules, routes and stops, track summaries, raw track points and check-ins. Raw points can be retained for a set period; trip and mileage summaries are kept. Roady owns the spatial record and the events it records. It does not own the task, the punch, the land file, the secret or the message that may follow an event.
4. Integrations and ownership
TaskMaster and TimeTracker use places and zones; LandMan, FarmDance and StockMan can point at the same records, and LandMan comparables use Roady’s place-to-place road distance. MediaMogul can hold imported map files or check-in photos. Conductor times retention. CosmosCall and TheIntegrator execute provider calls; KeyKook holds keys; Murphy receives problems. Roady writes location events; consumer apps decide what happens next.
5. Security and access
Access follows user, company and grant rules. Employee tracking applies only while a person is clocked in or on an active route; personal tracking is opt-in. Provider keys stay in KeyKook and are not fetched by the client for web-service calls. A visible map is not a grant to every place or track. Geometry and identifiers stay inside the owning personal or company boundary.
Competitive context
| Alternative | Its focus | CloudWinks product focus |
|---|---|---|
| Google Maps Platform | Maps, routes, geocoding and geofencing services. | A shared CloudWinks record of places, zones, routes and tracks that other apps point at. |
| Mapbox | Maps, navigation, search and geofencing for custom location apps. | Provider-neutral spatial records, with keys kept in KeyKook and calls made server-side. |
← More Foundation apps apps · All application briefs · How the framework works