Коопсуздук жана эксплуатация

Version dated 20 October 2026. An informational overview for customers and their IT teams. Contractual commitments are contained in the Order, the principal agreement, the SLA and the DPA; this overview creates no additional obligations or warranties unless its parameters are expressly included in an Order.

1. Infrastructure and access

The customer's production instance is hosted in the service region (DPA, Section 6). Development, test and production environments are separated; test environments normally use synthetic or test data, and exceptions required to resolve a specific incident are governed by the DPA. Engineers work from named accounts; administrative access to production systems and third-line support actions are logged under the internal security policy.

2. Backup and recovery

Backups are performed under Unitify's internal operational schedule, retained in the service region; selected restore procedures are tested under an internal schedule. Any specific frequency, retention depth, RPO, restore RTO, copy-placement scheme or test-restore frequency is binding only if expressly stated in an Order or a technical and organisational measures annex. This overview does not guarantee restoration to a particular point or within a particular period. The target restoration time for a Critical incident in Platform operation is defined in the SLA.

3. Integration interfaces (API)

3.1. The customer receives access to generally available API functionality included in the selected paid plan or Order, subject to documentation, permissions and applicable limits. The entities, queries and mutations of the generally available API are described in the instance's published GraphQL schema. Internal, administrative, partner and custom interfaces are excluded unless an Order provides otherwise.
3.2. Unitify may modify or deprecate API functionality. For the generally available API Unitify will, where reasonably practicable, give advance notice and migration information; any legacy-support period is set in the Order. Urgent security-, legal- or third-party-driven changes may be made immediately.
3.3. Request limits protect the Platform from overload and may change; any increase is at Unitify's discretion and may require a separate Order.
3.4. Webhooks: subscriptions to entity events delivered to a customer endpoint with retries; delivery is not guaranteed and customer-side handling must be idempotent.
3.5. A test environment with test data is provided where stated in an Order, for the period stated there and without an SLA.

4. Resident and staff apps

Unitify apps may be made available through the App Store and Google Play. Customer-branded (white-label) versions, their publication from the customer's developer accounts and their maintenance are provided only where expressly included in an Order.

5. Video surveillance and intercom equipment

Equipment is connected on a per-project basis where included in an Order, for equipment with open interfaces: cameras — RTSP/ONVIF, intercoms — SIP. Reference to a protocol does not warrant compatibility with a particular device model. The Platform does not perform facial recognition or other biometric identification by default. The location and retention period of the video archive are defined in the connection project. The Platform is not an emergency or life-safety system: where access-control, intercom or camera equipment is connected, the customer keeps a fallback means of access and its own emergency procedures independent of the Platform, and the Platform does not replace calls to the emergency services.

6. Performance

The Platform is built on an open-source core developed since 2020 and used in large residential property-management projects. Load testing of the customer's instance is performed where included in an Order; scope, scenario, timing and fees are set in the Order.