Frequently asked questions

Payment is available by credit card or bank transfer. Monthly payment is available for the Starter and Professional plans; Enterprise and on-premises deployment are billed annually. Annual payment is invoiced as a single amount, while monthly payment is invoiced each month.

Prices on the plans page are for the fiber module and are shown in TRY, excl. VAT. Users, projects, storage and training are listed on the same page. Use the payment period selector to review annual and monthly payment options. Terms specific to your organisation are defined in the agreement.

Additional users, storage, training days and data conversion services are listed on the plans page. Review the relevant price, scope and terms in that table. Data conversion is assessed according to the condition of your source records and the requirements agreed together.

When an on-premises deployment enters read-only mode because of its licence status, permitted viewing, search, reporting and export remain available; infrastructure data cannot be changed. The licence period and service and access terms are defined in your agreement. The licence status shown on screen indicates which operations remain available.

Version updates are included in the plans. Review current features in the release notes and usage steps in the user guide. For on-premises deployment, applying updates is assessed alongside your organisation’s infrastructure and the agreed service scope.

The network data belongs to your organisation. Authorised users can view data and use permitted output and export options. Your data retention and access requirements are assessed alongside the deployment choice; data handover and service terms are defined in the agreement.

For the cloud service, your data is hosted in data centres in Türkiye; backup terms are defined in the agreement. With on-premises deployment, the application runs on your organisation’s infrastructure. Data location, backup responsibilities and access requirements are assessed together when choosing a deployment.

Project access can be open to organisation users or restricted to project members. Organisation administrators can access their organisation’s projects. Project roles and the user’s organisation role apply together; the Viewer role supports viewing and permitted outputs without changing data.

Region and module selections restrict the records a user can change; they do not hide readable data by region. Use project access settings for viewing access, and writable region and module selections for team working areas. The project membership guide explains this distinction.

Export data as DXF, KML, GeoJSON and XLSX. A project package moves map features, supported devices, connections and settings to an empty project. Keep the original contents of photo, document and measurement files separately; a project package is not a backup of all organisation accounts and work history.

Change history shows data operations with the user, time, description and affected records. Authorised users can undo eligible operations. Later edits and record relationships can affect the result, so assess the operation’s scope alongside the check result shown on screen.

Import KML, KMZ, GeoJSON, Shapefile, CSV, DXF, GeoPackage and FileGDB data with preview and field mapping. Check the source coordinate system and target record types. A data conversion service is also available to prepare drawing and table records.

The schedule is defined during scoping. Source organisation, coordinate information, missing fields and the records to review during acceptance affect the plan. Identifying current files and internal data owners at the outset clarifies preparation and acceptance work.

When importing an update linked to a source record, the previous source, new file and local record are compared. Review field corrections and conflicts in the source difference report, then choose which changes to retain or apply. Keep the stable key field for the same source.

Address and building records are imported from your organisation’s sources or entered manually. SoSoMaps lets you organise these records alongside project information. Your organisation verifies source currency and field meanings, which guide import preparation.

A map of Türkiye is included with the system. Your organisation’s map services can be added for other regions and satellite imagery. Service access and usage terms are assessed separately; basemap selection and project network records are managed separately.

Deployment support, training, data conversion and the public documentation centre form part of the offering. Requirements are assessed alongside the selected plan and agreed services. Send support requests to support@soso-labs.com; requests are answered on weekdays 09:00–18:00 (Turkey time, excluding public holidays). The Enterprise plan and on-premises deployment include priority support and a telephone line; service times are defined in the agreement.

The training agenda reflects team responsibilities and intended use. It can cover projects and inventory, design and field work, operational outputs and organisation administration. The plans page lists the training included in each plan and the additional training day option.

The user guide and developer documentation are publicly available. The guide covers screens and workflows; developer documentation defines contracts for the API, access keys, map publishing and event notifications. Browse related topics and search within the documentation centre.

With the cloud option, you access SoSoMaps through a web browser and your data is hosted in data centres in Türkiye. With on-premises deployment, the application is installed on your organisation’s infrastructure and can also work without an internet connection. Deployment and operational responsibilities are assessed around your requirements.

The fiber module is available today. Electric, copper and coax modules are marked Coming soon. Review fiber inventory, connection, design, field and operations features on the features page, and their usage steps in the user guide.

The offline field application lets you work without an internet connection using a field package downloaded to the device in advance. Downloading a package and submitting changes require a connection. When connected, send changes and attachments for office review; adding them to the project record requires review and approval.

SoSoMaps is for recording and managing fiber infrastructure. CRM, billing and network monitoring are handled by your organisation’s relevant applications. Technical circuit and project records can reference external system identifiers; integration requirements are assessed through documented connections.

Use access keys with the documented API to read data and edit it with suitable permissions. WMS and OGC API Features provide read-only geographic data sharing. Webhook notifications send project events to other applications; the technical contracts are in the developer documentation.

A key is linked to a user; its project scope and write access are defined when it is created. It does not extend its owner’s current permissions. Revoke the key when it is no longer needed. The user’s or organisation’s access status also affects whether the key can be used.

The webhook definition specifies the target application, events and project scope. Notifications are signed, and the receiving application verifies the signature. Review results and errors in the delivery log. A queued notification does not mean it has been delivered to the recipient.