Questions about the platform.

ISB Security Platform is a multi-tenant operational software system designed for professional security organizations. It connects reporting, objects, personnel, operations, governance and AI-assisted workflows through one shared organizational, access and audit context.

Private security companies, mobile patrol providers, object and event security, retail, corporate, healthcare, education, municipal and government-contractor security operations. Buyers include operations managers, security coordinators, IT stakeholders and procurement teams evaluating operational software.

Fragmented security operations where reporting, object instructions, planning, messaging, personnel context and audit information live in separate tools or outside systems. The result is repeated administration, weak handovers, missing context and low traceability. ISB is designed to bring these into one controlled operational context.

ISB is one platform with modular capability domains. Domains such as reporting, objects, personnel and operations share the same identity, permission, tenant, object and audit foundations. Modules expand without becoming isolated products.

Yes. The architecture is multi-tenant and tenant-aware. An organization can manage multiple customers and objects while keeping operational context and access scoped. Cross-tenant data access without authorized context is not part of the design model.

Organization → Customers → Objects, with further location hierarchy (buildings, floors, zones, rooms, posts, checkpoints and assets). Users, roles, reports and operational actions attach to this structure so permissions and records remain context-aware.

ISB Security Solutions is the company. ISB Security Platform is the product — the operational software system the company is building for professional security organizations.

The platform is under active development. It is not presented as commercially production-available. Organizations can request a demonstration and discuss pilot or early engagement options.

Current foundation includes multi-tenant and access foundations, object/location hierarchy foundations, audit foundations, the Specific Report workflow, and the AI-assisted Specific Report MVP. Broader modules are in active development or planned.

Broader reporting workflows, notifications, escalation and supervisor workflows, deeper object and personnel context, mobile-oriented field usability and operational overview. See the Roadmap for the full staged view.

Core capability or architecture exists as part of the current development foundation. It is not automatically a claim that the capability is production-complete for every deployment scenario.

The capability is part of the intended platform direction but is not yet committed to release timing. Placement on the roadmap is not a contractual delivery promise.

Long-term product direction subject to research, validation and prioritization. Future direction items are not committed delivery and should not be treated as near-term availability.

No. The roadmap intentionally avoids quarter labels and artificial deadlines. Stages describe maturity, not a delivery calendar.

Yes. Priorities may change based on technical dependencies, validation outcomes, operational requirements and security considerations. The roadmap is current development direction, not a fixed schedule.

Yes. The platform is designed around shared foundations with environment-specific workflows — including object security, mobile patrol, events, retail, corporate, healthcare, education, municipal and government-contractor contexts.

Yes. Object hierarchy foundations include buildings, floors, zones, rooms, posts, checkpoints and assets so operational context can attach at the appropriate level.

Interfaces are designed with field use in mind. Mobile-oriented workflows and field usability are part of active development. Native mobile apps are not claimed unless released.

Mobile patrol is a supported operational environment in the product model. Route continuity, object context and rapid reporting are design goals. Broader patrol workflow expansion is planned or in development depending on the specific capability.

Offline-capable field workflows are an architecture direction and planned expansion item. They are not presented as fully released. The intended model is local workflow, reconnect, controlled synchronization, conflict handling and audit history.

Realtime foundations are being designed to support synchronized operational state for authorized users (for example incident status, review state, assignments). Guaranteed zero-latency or millisecond SLAs are not claimed.

Scoped customer visibility and customer portals are planned expansion. They depend on tenant and permission boundaries. Current focus remains the operator-side operational platform.

Assignments are part of the foundation model linking people to objects and operational context. Qualifications, certifications and availability are in active development. Scheduling foundations are planned.

Field notes can be structured into a draft Specific Report. Suggested extraction and language clarity support are available under the MVP. A human must review the draft. Where the workflow requires approval, a supervisor decides. AI does not finalize the official record alone.

AI can generate a draft from field input. The draft is not an official operational record until human review (and approval where required). Completeness suggestions are guidance, not legal validation.

No. AI assists with structure, clarity and extraction. Operational judgment remains with authorized personnel.

No. Approval is a human responsibility where the workflow requires it. AI cannot approve or finalize reports on its own.

Authorized users — typically the reviewing officer and, where required, the supervisor. Human accountability is central to the AI operating model.

No. AI does not make final operational decisions, replace escalation procedures, replace supervisors or determine legal compliance.

The AI-assisted Specific Report MVP: structured drafting, language clarity support, basic information extraction and a mandatory human review workflow.

Operational insights, pattern detection, risk signals, recommendations, Talent & Operations Intelligence and the Team Compatibility Engine. These are staged as planned or future direction and are not current production claims.

Future decision-support directions for role-fit insight, training recommendations and team composition support under human review. They are not automated hiring systems, personality diagnosis tools or systems that make employment decisions without human judgment.

Through tenant-aware data boundaries and context-scoped access. Shared platform services sit above organization separation. This is not a claim of complete cryptographic isolation guaranteed in every scenario.

Yes. The platform is designed around least-privilege role and permission scopes for roles such as officer, supervisor, customer representative (planned expansion) and administrator.

Critical operational actions are designed to be logged and associated with users — for example report creation, review, approval and key configuration changes. Traceable operational actions are the goal; legal immutability is not claimed.

No. ISO 27001 readiness is a future compliance direction. No certification is currently claimed or promised.

External security testing is part of planned validation. It is not presented as a completed claim on this site.

Design aims to collect operationally relevant data, limit access by role and context, separate organizational data and review retention. The product is designed with European privacy requirements in mind. Full GDPR compliance certification is not claimed.

Backups, recovery procedures and restore testing are planned validation items. Specific RPO/RTO figures and backup frequencies are not published as tested claims.

Security researchers, customers and organizations can report potential issues to info@isbsecuritysolutions.nl. No separate bug bounty or response SLA is claimed beyond direct contact.

Yes. ISB is designed as a multi-tenant SaaS model with tenant-aware data boundaries and shared platform services.

API foundations and a controlled external access boundary are part of the architecture direction. Broader API integration is planned. Specific third-party integrations are not claimed unless implemented.

Integration is a planned direction through controlled API boundaries that respect tenant and permission controls. No inventory of live integrations is claimed on this site.

As a planned expansion: local workflow, temporary offline state, reconnect, controlled synchronization, conflict handling and audit history. Not claimed as fully released.

The architecture is intended to support mobile-first field use. Mobile workflow foundations are in active development. Native apps are not claimed unless released.

Realtime foundations are being designed so authorized users can receive synchronized operational state. Event → platform → authorized users → updated state is the conceptual model. No latency SLA is claimed.

Yes. Capability domains consume shared foundation services (identity, permissions, audit, notifications, data context, API, storage). New modules are not intended to require rebuilding the core. Microservices are not claimed unless that is the actual implementation style.

Use the Request Demo form on the website. Provide operational context so the conversation can focus on relevant environments and current platform maturity.

Yes. Pilot conversations are welcome. Pilot acceptance is not guaranteed; fit, readiness and capacity determine whether a pilot proceeds.

Technology, industry and strategic collaboration conversations can be started via Contact. No formal partnership program is claimed on this site.

Security organizations evaluating the platform, pilot partners, strategic stakeholders and parties with general company or platform enquiries. Contact: info@isbsecuritysolutions.nl.

ISB is based in Tilburg, The Netherlands, with an initial focus on the European security industry. It is not limited exclusively to Dutch organizations.

International scalability is part of the long-term direction. Current focus remains European security operations. International offices or market presence are not claimed.