Stable core
Organizations, users, access rules, tenant separation, audit history, files, localization, versioning, publishing, rollback, and shared design foundations belong to the governed core.
The IntelCit platform
One city-intelligence foundation. A different fit for every team.
IntelCit combines a stable, governed core with configurable services, capabilities, permissions, workflows, language, and presentation. Municipalities receive what their operations need without creating a separate software fork for every customer.
A platform assembled around the customer
The same governed foundation can support different municipal outcomes by composing five clear layers.
PlatformShared identity, security, audit, data, localization, and release controls.
ProductsOutcome-focused service bundles a municipality can adopt.
CapabilitiesReusable building blocks such as capture, mapping, review, analytics, and reporting.
FeaturesSmaller controlled behaviors enabled for the right service, role, or pilot.
Customer configurationThe enabled combination, settings, permissions, language, and presentation for one organization.
Stable where trust matters. Configurable where operations differ.
Security and governance remain consistent while each organization can receive a focused operating experience.
Configurable experience
Enabled services, navigation, landing views, workflows, fields, dashboards, reports, roles, integrations, branding, and language can vary within controlled boundaries.
Controlled boundaries
Accessibility, security, status meaning, responsive behavior, auditability, data ownership, and release controls do not become optional when a customer experience changes.
A disciplined path for new customer needs
IntelCit starts with the smallest durable change and promotes only proven, repeatable needs into the standard platform.
- ConfigurationUse existing settings and contracts without new product code.
- ExtensionConnect a standard adapter, integration, export, rule, or widget.
- Custom moduleIsolate a customer-specific need behind platform contracts instead of forking the product.
- Standard capabilityPromote a proven reusable need into the shared IntelCit catalog.
Three clear experience boundaries
Public information, customer operations, and IntelCit internal controls remain separate even when they share one design system and deployment during the MVP.
Public website
Explains the platform, current services, evidence, trust approach, documentation, and demo journey.
Customer product
Shows only the services, data, actions, and reports enabled for that organization and user.
IntelCit console
Keeps customer management, service configuration, experiments, system operations, and protected knowledge internal.
What is working now
The MVP already has a versioned bilingual service registry, role-aware navigation, shared responsive shells, and three evidence-backed services at honestly labeled delivery stages.
MVP boundary: IntelCit is not yet an unrestricted page builder, workflow builder, marketplace, billing system, or production-ready implementation of every future capability. Those remain design directions, not current product claims.
Explore the right starting point for your city
A guided demo can focus on the current service evidence, the customer operating experience, and how a controlled configuration could fit your team.