All-Source Intelligence Fabric at Global Scale

If you think of the workflow as acquiring raw data, converting that data into a common format, assessing what the data means (both in itself and in context), and then publishing events relating to the data and it's meaning, the Isophene Nexus module does that at the rate of 1.25 million events per second for each node (or server) that is deployed. That means that Nexus can ingest huge quantities of data, from a variety of sources, in order to deliver events that further assessments and decisions can be based upon. Moreover, the 'per node' aspect means that, if a customer requires it, Nexus can scale horizontally: doubling the throughput with each additional node.

Isophene operates a distributed global messaging system that routes events from the Isophene Nexus module to subscribers worldwide. Subscribers include our internal systems as well as customer deployments and our mobile and desktop applications. As Isophene Nexus emits events, those events are sent over our global messaging system and are delivered, on average, within 120 milliseconds of being emitted. Think of this as 'WhatsApp' for events: a private messaging system that gets event information to wherever it is needed. This means that there is minimal delay from the time data is acquired to the time it can be employed to generate actionable insight. However, if Isophene is deployed within a customer organisation and operating on sovereign data, event distribution is at the wirespeed of the customer's network.

For the Isophene internal deployment, open-source data feeds are used to deliver a range of subscribable events, as well as assessed intelligence, to customers. Our primary feeds are updated at rates commensurate to the nature of the feed and/or the entity type the feed relates to. For example, if we provide an aircraft event feed then the update rate would be measured in seconds while a vessel event feed update rate would be measured in minutes. Other feeds will have different update rates on the same basis. Our entity and location based feeds, which represent aggregated events from multiple data sources that relate to a given entity or location, are updated as soon as a new event occurs regardless of the data source the event is from. For customer deployments against sovereign data, the update rate is entirely at each customer's discretion (although we do recommend thinking through the nature of the data source first!).

The Isophene platform has been designed to support a wide range of deployment options. At the most basic level, customers can simply subscribe to event streams and assessed intelligence outputs from Isophene's internal deployment. Beyond that, because the Isophene platform has been designed as a set of modules, there is a sliding scale of capability deployment on the customer side: ranging from a pure web or mobile application client through to a full platform deployment. When software, as distinct from subscriptions, is licenced to a customer, it can be deployed on-premise or in the customer's chosen cloud. However, for sovereign applications, we strongly recommend reviewing the potential impact of the US CLOUD Act in relation to cloud deployments. We'd be happy to walk through what you want to achieve and define a deployment architecture that works.

The Isophene platform has no commercial third-party dependencies. We do not need, for example, Esri mapping or Microsoft SQL Server to deliver a functional solution. Where there are traditional dependencies, such as on databases or operating systems, we deliberately choose to build on top of permissively licenced open source software such as PostgreSQL and Ubuntu Linux. Of course, if you already have legacy third-party software that you have to maintain and if open standards permit, we are able to integrate with what you have already invested in. Our integration mindset allows you to create an event 'superlayer' over what you already have and, then, to use that as a foundation for future value.

Good question! At the most basic level, you can subscribe to event streams and assessed intelligence outputs and pull those straight into your own systems. The next level up is very much a 'Software-as-a-Service' model, in that we host the application and you access and use it through a pure web or mobile client application. However, when you want to start incorporating your own sensitive or sovereign data and analyses, we strongly recommend that you operate your own instances of the relevant platform components: inside your network boundary (on-premise, cloud, or hybrid) and under your control.