Evaluation checklist
What to look for in a survey data delivery platform
Sixteen questions worth asking before you choose where your point clouds, orthomosaics, scans and drone data go when they leave your office. Each one has Swyvl's answer, including the ones it cannot yet say yes to. Ask every vendor the same sixteen.
1. Does the client need software or an account to open it?
YesNo. A share link opens in any browser with nothing to install and no login. You can add a password or restrict the link to named people, and change that after it has been sent.
2. Can it open the formats we deliver?
YesPoint clouds (LAS, LAZ, E57, PTX, PTS, XYZ, PLY), orthomosaics and DEMs (GeoTIFF, COG), 3D Tiles, meshes (GLB, glTF, OBJ, FBX, STEP, IGES), BIM (IFC), CAD (DXF), Gaussian splats (PLY, SPZ, KSPLAT, .splat), XGRIDS LCC and LCC2, vector data (GeoJSON, KML, KMZ, SHP, GPX), drone video with GPS (DJI SRT), 360° photos and video, PDFs and images. A file with no viewer is still stored and downloadable, and the card says why.
3. Can we send everything from a job in one link?
YesYes. A share link covers a site, so every file from the job goes out on one link, each in its own viewer, with a filmstrip between them. Files can be added after the link has been sent, and a link can be set to include future uploads.
4. Can the client measure on it?
YesYes. Point, distance, area and height tools on every 3D and map viewer, on the hub and on share links, on every plan. Every measurement carries a badge saying which frame its numbers are in. A client's measurements change nothing in your delivery; your team can save a measurement as a note, pinned to the spot. There is no volume tool.
5. Can we control viewing versus downloading?
PartlyPer link, yes: view-only or view-and-download, and you choose which files each link includes. Download rights are set per link, not per file within one link.
6. Can we restrict a link to named people, or password it?
YesYes. Open to anyone with the URL, password-protected, or restricted to named people by email. Passwords are enforced on the server with lockout after repeated failures. All three can be changed after the link has gone out, and a link can be revoked at any time.
7. Is there an audit trail of who opened what, when and from where?
YesYes. Every view is logged with the time, the file and where it was opened from, and appears in the site's activity feed straight away. The log is append-only at the database level and is kept for two years.
8. Is each delivery dated, and can we see a site over time?
YesYes. Every upload becomes a dated collection on a permanent site. In your workspace the site's timeline lays the collections out by date. A share link set to include future uploads shows each new collection as it lands.
9. Where is the data stored, and does it leave that region?
YesYou choose one of eight regions when the organization is created: Australia, US East, US West, United Kingdom, Europe, Canada, Japan or Singapore. Your files are stored in the region you choose, and the region is fixed for the life of the organization. Some processing and display steps, such as rendering map tiles and preparing downloads, can run on Swyvl's servers outside your region.
10. Can we get everything back out in standard formats?
YesYes. Every original file stays downloadable in the format you uploaded, and derived versions are open standards: COPC, COG, 3D Tiles, GeoJSON. On cancellation the account enters a 30-day read-only export period.
11. Can the client upload back to us?
PartlyNot through a share link today. Invite them to the workspace as an editor and they upload straight to the site, with every upload logged against their name. Remove the editor when the job ends and the files stay with the site.
12. Can the client comment on it?
YesYes. Pin a note to a point, an outline or a saved measurement on a point cloud, orthomosaic, 3D Tiles model or XGRIDS scan, with a sketch and attachments. Clients you invite by email reply on the note, free, with no account; public and password links are view-only. Notes follow the place, so they show on the next capture of the same spot, and export as CSV, GeoJSON, JSON or ZIP. Not yet on 360° photos or on Gaussian splats other than XGRIDS. How notes work.
13. Can we brand it?
YesYour logo and colors on every share link on paid plans. Full white-label, with no Swyvl branding, on Enterprise.
14. Can we control who in our own team sees what?
YesTwo levels. Organization roles (owner, admin, member) govern billing, seats and settings. Workspace roles (owner, editor) govern access to the data. Contractors can be invited as editors and removed when the contract ends; the data stays with the site.
15. Single sign-on and SAML?
On requestGoogle sign-in and passwordless email sign-in with optional two-factor authentication are standard on every plan. SSO/SAML is an Enterprise feature, available on request and scoped per engagement.
16. Is it certified?
Not yetNot yet. Swyvl's controls are aligned to ISO 27001 and SOC 2 and mapped in a control register, and SOC 2 Type I is the first certification target. In place today: passwordless sign-in with optional two-factor, row-level access control on every table, an append-only audit log kept for two years, encryption in transit and at rest, file storage in the region you choose, no training on customer data and file contents never sent to AI, a published subprocessor list, and access-review, personnel, change-management and secrets policies. A supplier security questionnaire is available on request.
The checklist, to paste into your own evaluation
- Does the client need software or an account to open it?
- Can it open the formats we deliver?
- Can we send everything from a job in one link?
- Can the client measure on it?
- Can we control viewing versus downloading?
- Can we restrict a link to named people, or password it?
- Is there an audit trail of who opened what, when and from where?
- Is each delivery dated, and can we see a site over time?
- Where is the data stored, and does it leave that region?
- Can we get everything back out in standard formats?
- Can the client upload back to us?
- Can the client comment on it?
- Can we brand it?
- Can we control who in our own team sees what?
- Single sign-on and SAML?
- Is it certified?
See it answered in practice: use cases by problem · features · security documentation · subprocessors