g.on experience

Scenarios where alternatives are likely more appropriate

• Organizations that require an extensive corpus of independent public reviews and benchmarking data should consider vendors with a broader public footprint, as public third-party review content for g.on is limited.
• Buyers seeking transparent, self-serve pricing and trial options may prefer lighter SaaS tools; g.on pricing is primarily quote-based.
• Organizations standardized on Esri that rely on deep ecosystem integration and Esri-native extensions may find extending the existing Esri platform to be more efficient than introducing an alternative framework.
• Organizations without the budget or capacity to fund customization and change management should consider off-the-shelf solutions or managed services with clearer low-touch deployment models.
• Buyers requiring immediate access to public documentation for SSO/SCIM/audit logs and specific data residency assurances should verify these details before shortlisting, as public documentation for these items was not located.

Current limitations acknowledged by the vendor

• No explicit vendor-published limitations were identified in accessible public materials.

Features on the roadmap (not yet available)

• Roadmap items were not publicly documented in the sources reviewed.

Scale limitations

• No public documentation describing scale limits was identified.

Security or compliance gaps

• SOC 2 and ISO 27017/27018 were not publicly documented. Public detail for SSO/SCIM/audit logs/encryption specifics was not found.

Technical debt or architectural limitations mentioned in reviews

• No public review data was available to assess reported technical debt or architectural concerns.

API limitations or integration constraints

• API and integration specifics are not widely documented in public materials; the vendor emphasizes interoperability via OGC services.

• There is insufficient independent customer review data available in public sources to validate unique selling points based on third-party feedback.

• The vendor markets a modular geoportal framework (aimPort) integrated with workflow management (pm) and mobile field capture (field), presented as a combined solution set for asset and operations management.
• Vendor materials emphasize airport operations and regulatory use cases as a target vertical.

• Distinctions are primarily based on product design focus and vendor positioning (e.g., tailored geoportal plus integrated workflow and field capture). Buyers should validate feature coverage and integration capabilities through demonstrations and reference checks.

• Larger vendors such as Esri have broader ecosystems, more extensive public documentation and training resources, and a larger talent pool. Open-source approaches offer different cost and control trade-offs.

Availability of third-party reviews for g.on (key limitation)

• Major review platforms and marketplaces: no accessible product listing or review corpus for "g.on aimPort" or "g.on experience" was found during this research.
• Searches of public community forums and discussion sites did not surface substantive user review threads specific to the product.

Vendor-published testimonials / internal quotes (not independent)

• The vendor publishes internal employee quotes and event collateral. Example: an internal employee quote describing involvement in product design was found on a careers page.

What customers reportedly achieved / why they choose it (evidence constraints)

• Airports and compliance-oriented use cases: event collateral states aimPort is live at certain airports and frames the product as aligned to specific EU regulatory requirements. These are vendor-authored statements and were not corroborated by independent third-party sources.
• Historical claims about training requirements were identified in older vendor materials; such claims are dated and not treated as current evidence.

Balanced view: what’s missing

• Independent, third-party review content is scarce or absent in accessible sources. Buyers should plan for reference checks, pilot evaluations, and direct technical/security assessments to validate vendor claims.

• Düsseldorf Airport / DUS Airport Map
  • Vendor materials state that a delivery for Düsseldorf Airport used aimPort for airport operations and claim the project was delivered "on time and on budget." Event collateral reiterates the deployment and references regulatory alignment.
• Aviation footprint claim
  • Event materials state use by a number of airports; the methodology for counting and the scope of those engagements was not disclosed in accessible collateral.

• No independent project documentation or third-party confirmation was found.

• These are presented in vendor event collateral; the basis for counts (active deployments, pilots, past projects, or modules used) was not disclosed.

• The vendor references regulatory requirements; buyers should request feature-level traceability to requirements, evidence of audits where relevant, and update commitments as rules evolve.

• g.on aimPort: a framework for creating browser-based geoportals for asset and infrastructure management, integrating multiple data sources, and applying role-based access down to layers and attributes. The product supports OGC-conformant web services and provides map and attribute-table user interfaces.
• g.on pm: a process management and workflow digitization module that integrates with aimPort for approvals, infrastructure requests, and permit-like processes.
• g.on field: a mobile application for field data capture and editing with online/offline synchronization and optional external GNSS receiver connectivity via Bluetooth.

• Aviation and airports
• Chemical industry sites
• Natural resources and mining
• Public infrastructure and municipal operators