Aptli brings GIS into daily operations.

Aptli connects to the systems you already run.

• Aptli exposes a REST API, accepts inbound push authenticated by key, and polls a source you name on a schedule.
• Outbound webhooks are signed and their deliveries are logged.
• Aptli reads and writes directly to Postgres and SQL Server.
• Two-way ArcGIS feature service sync, plus packaged connectors for Geotab telematics, RSS and any HTTP or JSON source.
• Scheduled extracts go out as JSON, CSV, GeoJSON or PDF to a directory, a storage bucket, an endpoint or an inbox.
• A named ERP, CRM, financial or document management system is reached through the HTTP lane, a direct database connection or a scheduled file exchange.
• One line of script places the map, a form or an intake queue into pages you already have under your own domain.
• Aptli CMS is a separate product that runs the whole public website. The portal is native to it rather than embedded, and the two share one login and one hosting arrangement.

• REST API
• Inbound push
• Scheduled polling
• Signed webhooks
• External database read and write
• Aptli CMS
• Reply by SMS or email
• Embed script

Getting the record back out in the formats a finance team and an auditor expect.

• Record types across the system export to CSV, Excel, PDF and GeoJSON.
• A read-only feed API returns any saved view as JSON or GeoJSON to a scoped key. The view is the boundary. A key only ever sees what that view exposes.
• An append-only audit log exports to CSV, JSON and XLSX.
• Scheduled extracts on a timetable you set, delivered where you choose.
• A validated inspection issues a branded PDF of record.
• Usage analytics are first-party and need no cookie banner.

• CSV, Excel and PDF export
• Read-only JSON and GeoJSON feed API
• Templated documents
• Audit event log
• Scheduled extracts

Who can reach what, enforced at the query layer.

• Single sign-on runs over SAML 2.0 and OIDC. That covers Microsoft Entra ID.
• Identity-provider groups map to Aptli roles. Unconfigured it is a no-op.
• Multi-factor authentication by authenticator app or SMS. One-time recovery codes are issued at enrolment.
• Rights granted per record type and per operation. The server refuses the query rather than hiding the control.
• Record-level restrictions sit on top of role rights.
• Contractors and external parties take work without consuming a seat.
• An append-only audit log records who did what, when, and whether it passed.

• SAML 2.0
• OIDC
• Microsoft Entra ID
• IdP group mapping
• Authenticator app or SMS MFA
• Rights at the query layer
• Record-level restrictions
• One instance per customer
• Data residency you choose

Changes arrive for review rather than landing straight in the record. Earlier versions are kept.

• A field crew stages geometry and attribute changes as a draft. An administrator sees the diff and any collision it would cause, then approves or rejects from a queue.
• Undo and redo run across a whole editing session. Staged changes are held until an explicit commit rather than written on every keystroke.
• Compare any two versions side by side, discard one or restore an earlier state.
• An import previews its field definitions before it lands. Overlaps and duplicates become map markers you resolve before the import commits.
• A completed report is submitted for review. A reviewer returns pass, fail or needs-revision with comments.
• A connected system such as ArcGIS receives committed records only. Work in progress is never pushed outward.

• Draft and commit
• Undo and redo
• Diff and restore
• Import preview
• Review verdicts
• Commit-gated sync

The same system installed on a desktop, a phone and a tablet in a truck. It keeps working off the network.

• An installable web app on iOS, Android, Windows and macOS, straight from the browser with no app store. Updates arrive without a store review.
• Offline capture syncs when signal returns.
• Photo and video capture record the GPS accuracy of the fix beside each file.
• Dictation runs on the device itself on phones and tablets. QR scanning and signature capture are built in.
• An iCal feed publishes scheduled work to a calendar.
• Interactive tours run inside the app, and an assistant helps staff complete a record as they work.

• Installable web app
• Offline capture and sync
• Photo into the report
• Spoken completion report
• QR scanning
• E-signature
• iCal feed
• In-app tours

Getting word to the people who need it on the channel they use.

• Notifications go out by email, SMS and push.
• People subscribe per notification type and opt out by channel.
• Staff raise help requests, and administrators send broadcast messages.
• Four languages run across the platform, the public portal and the website.
• Issued documents carry your logo and titles.

• Email
• SMS
• Push
• Subscriptions by channel
• Four languages
• Your brand on documents

Guidance inside the app on a provider you choose. Identifiers are stripped before anything leaves the instance.

• It is built into the app and knows which screen and form you have open. Guidance is about your own configuration.
• An administrator chooses the provider and model. A self-hosted endpoint keeps inference inside your own country.
• Names, emails and phone numbers are replaced with deterministic tokens before a request leaves the instance. The reverse map stays in your own database and the substitution is auditable.
• It proposes and a person applies or discards. It does not commit changes on its own.
• It answers on data explicitly shared with it, inside the same role scoping as every other screen.
• It is disabled on a new instance and stays off until an administrator enables it.

• In-context guidance
• Provider choice
• Self-hosted in your own country
• Identifiers pseudonymised
• Ships disabled
• Proposes, never commits
• Scoped to shared data

The register, and the map it lives on. Your GIS remains the authoritative source.

• Every asset carries category, condition, install date, replacement cost, useful life and criticality.
• Watermains, hydrants, roads, bridges, streetlights and benches ship with useful life and criticality already set.
• A parent-child hierarchy spans linear and vertical assets.
• Two-way ArcGIS feature service sync. Write-back is configured per deployment and covers rows carrying an integer OBJECTID.
• Import reads Shapefile, File Geodatabase, GeoPackage, MDB, DXF, DGN, GeoJSON, KML, KMZ, CSV and Excel.
• A preview flags overlaps and duplicates before anything commits.
• A layer carries its own field schema. Every feature on that layer is the same kind of thing and carries the same typed properties. Defaults are pre-filled on commit.

• GIS-anchored register
• Configurable attributes
• Parent and child assets
• Lifecycle fields
• Audit history per asset
• Bulk import
• ArcGIS URL connection
• Collision detection on import
• Geodatabase write-back

The half of the work that happens away from a desk.

• Forms, checklists, required fields and validation rules are all configurable.
• An inspection raises a deficiency, and the deficiency raises a corrective work order against the same asset.
• Crews work from the map against the asset they are standing next to, not from a list.
• Evidence attaches to the record at the moment of capture rather than afterwards.

• Configurable forms
• Checklists and required fields
• Deficiency to corrective work order
• Qualification check by tag
• Evidence capture
• Review verdicts

Raising work against a mapped asset, assigning it and closing it out.

• The same work order shape is used across asset classes.
• Assign to staff, crews or external contractors. A contractor needs no seat and no licence.
• Preventive maintenance fires on calendar, meter reading and condition triggers.
• Stages, fields, forms, validation rules and permissions are administrator configuration.
• Two people editing the same thing raises a conflict for review rather than overwriting one of them.
• Open items carry due dates and overdue tracking.
• Escalation rules decide who is notified when work goes stale. They compile down to ordinary automations workflows and run through the same engine and audit trail.

• Work orders against a mapped asset
• Individual accountability
• Status workflow
• Work-collision detection
• Recurring schedules
• Notification lead times
• Overdue handling
• Sensor-threshold triggers
• SLA timers
• Escalation rules

The public surface residents actually use, and the intake behind it. It lands as work rather than as email.

• The public submits with attachments and receives a reference number. No account is required.
• The portal map shows only the layers you publish, and only the properties you mark public on each one. Everything else stays internal.
• A resident describes the problem out loud and the right form is picked for them. The model sees the form titles and nothing else.
• A photo and a spoken description fill the form fields in before anyone types.
• The public form captures photo, voice, QR and signature.
• A submission arrives in a triage queue rather than in the work list.
• Staff convert it to a work order against the mapped asset in one server-side step.
• Status returns to the submitter through to completion.
• The portal runs on your own domain with DNS verified before go-live, or embeds into a site you already have with one line of script.

• Anonymous with reference number
• Published map subset
• Voice-routed forms
• AI form fill
• Photo routing
• QR entry
• E-signature
• Triage queue
• Status notifications
• Custom domain
• Embeddable

Condition now, and what it will cost later.

• Condition assessments are append-only and can be backdated. An older reading does not overwrite a fresher one.
• Remaining useful life and a ten-year replacement forecast derive from that history.
• Criticality is carried per asset.
• A graduation log records an asset moving between layers.

• Condition history
• Remaining useful life
• Ten-year forecast
• Criticality

Where every part is, who is holding it, and what it was used on.

• Stock is held per site, and transfers move it between sites.
• Every worker has a personal stock account. What is signed out stays on their name until it is used, returned or handed on.
• A transfer is offered and accepted rather than pushed. The recipient can decline it and the sender can cancel it before it lands.
• Facilitated pickups dispense stock to a named person, and a QR handoff moves it directly between two workers.
• A stocktake reconciles a physical count against the record. Each varied line writes its own adjustment and one audit event in a single atomic pass.
• Receiving, adjustments, consolidation and conversion are recorded as transactions rather than as edits to a number.
• Consumption is recorded against the work that used it, and material that was not used is returned to stock from the same report.
• A photo of an unfamiliar part is turned into tags and matched against the catalogue.
• Holdings and transaction history export to CSV and Excel, and items load in from the same templates.

• Stock by site
• Personal stock accounts
• Site transfers
• Offer and accept
• Facilitated pickup
• QR handoff
• Stocktake reconciliation
• Consumption against work
• Returns
• Photo part lookup
• CSV and Excel