The cloud layer between your data and your users

Yes. Organise content by year, project and layer; combine predefined folders and user groups to isolate access per client or contract.

Yes. Create temporary users and set access dates from user management. Administrators control provisioning, expiry and revocation.

Yes. Viewing permissions apply per layer and per user group: each user sees only the layers they are authorised for.

Session control and user management are built in. Formal audit requirements (logs, retention, export) are scoped per deployment against your compliance needs; we do not assume a standard audit pack without a technical review.

Yes. Distributed storage architecture supports multiple locations and regions. During scoping we define region, latency and requirements per project and client.

SSO/SAML integration with corporate directories is not part of standard SaaS. We assess it for enterprise deployments when it is a project requirement.

The architecture is built for large catalogues, progressive streaming and distributed storage. Practical limits depend on formats, layer count and concurrent users. We scope this in a diagnosis with real datasets, not generic marketing figures.

Yes, in most cases. Obliquo Cloud replaces bespoke portals or scattered FTP handovers while keeping your sources and production workflows. We review which layers, permissions and URLs should coexist or migrate in an initial pilot phase.

Through user groups, predefined folders and content organised by year, project and layer. You can set layer-level viewing permissions, temporary users and access dates from user management.

Yes. At organisation level you can connect WMS, WMTS, WFS, ArcGIS and 3D Tiles. From the viewer you can also add third-party services per session and promote them to permanent layers when needed.

It integrates. ArcGIS and QGIS remain production tools; Obliquo adds web publishing, permissions and browser access. QGIS and ArcGIS Pro plugins connect production workflows to cloud publishing.

Yes. The development API is the same surface the Obliquo application uses. You can integrate ingest, publishing, viewing or permissions into your portal, GIS or custom flow without being limited to our UI.

Datasets in supported formats, an owner for users and permissions, and clarity on who publishes versus who consumes. Viewers only need a browser. We start with a diagnosis: formats, volume, permissions and integration with your current GIS stack.

It depends on formats, volume and integration depth. A pilot with one representative dataset can move in days; deployments with advanced permissions, multiple sources or infrastructure requirements need prior planning. We validate value before scaling.

We review hosting, region, access and architecture per project, especially for public sector, critical infrastructure or sensitive data. We do not assume one SaaS model fits every case without a prior technical diagnosis.

Yes. Obliquo Cloud unifies terrain, meshes, point clouds, GIS layers, raster, vector and imagery in one browser-based 2D/3D workspace with a coordinated layer tree and viewing modes.

Yes. Any camera dataset works when external orientation (EO), OPK angular format and full camera calibration are available.

No. The Obliquo web application is built directly on the development API and always tracks the latest version.

Not currently. Supported raster delivery includes TMS, WMS and WMTS. COG is on the roadmap.