Physical Security Information Management (PSIM) unifies the monitoring and control of connected security systems. Events and device information are brought together to support a consistent view of the installation.

Identity, Credential and Access Management (ICAM) brings identities, credentials and access rights into a common management environment for connected access control and alarm systems.

Command & Control connects information with action. Operators can issue commands through the platform, while automated workflows help connected systems and users work together.

Monitor the health, availability and status of connected devices around the clock. A unified view helps operators follow conditions across different technologies rather than checking each manufacturer's software separately.

Send supported commands directly from C4, such as an instruction to open a door. Where the integration provides configuration functions, manage device parameters in the same environment instead of switching to a separate device application.

Manage identities, credentials and access rights centrally. C4 provides a unified approach to access administration across connected access control and alarm systems, bringing related information and permissions into one place.

Smart Routines support automated processes based on application or external-system events, device status and user activity. Actions can include device commands, email or SMS notifications, client-application actions and customer-specific extensions.

Collect events from connected devices in a central database for reporting, auditing and security analysis. Reporting extensions can support reusable reports and customer-specific processing of report data.

Define what each user can see and do according to their responsibilities. C4 supports role-based access and fine-grained permissions, including restrictions at the level of individual devices in complex installations.

Simple Client is not limited to a narrow data export or an isolated device connection. It provides methods to access and manage C4 data within the assigned permission scope. This makes it a foundation for customer-specific data processing, tailored interfaces and interactions with connected systems.

Access is mediated by the application server, so extensions work with the C4 data model and permission framework rather than accessing the C4 SQL Server database directly. Partners can focus on the customer's requirements instead of creating a separate database-access mechanism for each extension.

Simple Client supports both transaction calls and message-based communication. Transaction calls retrieve or modify data. For example, an application requesting a list of persons receives only the records that the current user is allowed to see, because the server evaluates the request and filters the result.

Message communication enables interactions between applications, services and plugins. An authorized "Open Door" command, for example, can be routed through C4 to the responsible Driver, which sends the supported instruction to the device. An application can therefore combine access to information with operational actions through one integration approach.

Developers can use the shared interface when building Drivers, IS Connectors, Panels, Smart Routines and reporting extensions. A C4 plugin host initializes Simple Client and makes it available to the hosted plugin, giving extensions a common route to the application server.

C4 also supports independent applications that use the platform to monitor and manage devices. This creates scope for customer-specific applications that use C4 as their integration foundation instead of duplicating connections to each supported device. Their functional scope and licensing are defined separately for the project.

The SDK provides a .NET-based development interface. Its connector layers handle tasks such as user login, local caching, time-zone conversion, communication with the application server and server-side permission evaluation. Developers work with the Simple Client interface rather than separately implementing each stage of that communication path.

This shared foundation can reduce repeated integration effort and help development teams concentrate on customer-specific logic and the user experience. Each extension retains its own development, deployment and maintenance lifecycle, allowing the partner to manage its functionality as a distinct part of the solution.

Permissions are evaluated on the server, with separate permissions for operations such as reading, adding, changing and deleting data. Access can be defined at the level of individual records, so an integration can be limited to its agreed information and responsibilities instead of receiving unrestricted access to the installation.

External Simple Client connections use encrypted and authenticated HTTPS. The authentication strategy is selected for the deployment; the security specification requires OpenID Connect for Enterprise Security. Internal communication channels have separate security characteristics and must be assessed as part of the deployment design.

For users, Simple Client provides a route to software that fits their operating processes while continuing to use C4 as the common integration and management platform. A customer-specific interface can work with permitted C4 information and supported commands instead of introducing a disconnected operating tool.

For partners and developers, the API opens opportunities to deliver specialized applications, reusable extensions and project-specific workflows. The combination of a shared interface and SDK documentation supports a consistent development approach, while the partner contributes the industry knowledge and functionality that make the solution relevant to the customer.

Training supports the skills needed to work with the platform. Licensing and project services help manage the installation scope, while the Plugin Store provides access to the extensions used in customer projects.

Partners can build solutions from the platform's integration and customization capabilities. Developers can create plugins under a developer agreement with Gamanet, with responsibility for their own extensions defined separately from the core platform.

SDK Documentation on the C4 Wiki complements the Simple Client API with a dedicated documentation resource for developers. It gives teams a reference point for their C4 development work, helping them build their understanding of the platform before implementing an integration or extension.

Developers can use this resource during project preparation, implementation and maintenance. Together with the shared API, it supports a more consistent approach to development and helps partners evaluate C4 as a foundation for customer-specific solutions. For users, this creates a clearer route from an operating requirement to an extension developed within the C4 ecosystem.

The developer ecosystem extends beyond writing code. For integration plugins, the security specification defines verification of the plugin's use of C4 interfaces and certification of its communication with an external system as separate requirements before customer release. This provides a framework for planning quality and security reviews alongside implementation.

Distribution through the Plugin Store, digital signing and installation approval connect development with a managed delivery process. Combined with SDK documentation, platform training and a developer agreement, this gives partners a structured route for turning their expertise and customer requirements into C4 extensions.

A C4 installation combines a server license, called an Edition, with the required plugin licenses and other extensions. The Edition defines the functional scope, applicable C4 version, usage period and server scope. Plugin licensing defines the relevant integrations, device quantities or additional functions.

For drivers, the item being licensed depends on the particular integration. The required Edition, plugins, deployment scope and any upgrade needs should therefore be confirmed as part of the project specification.

Independent applications that use C4 for device monitoring and management have a separately defined licensing scope. Projects that include custom development should confirm the intended API operations, the required permissions and the applicable plugin or application licenses during solution design.

Where the solution includes a custom application or plugin, involve the developer when defining the data, commands and user experience the project needs. Agree the scope of the extension, its permission boundaries, the external interfaces it must use and the responsibilities for testing and maintenance. Use the SDK documentation and the security specification as references when preparing the implementation.