Try GeoLens on a real workflow for four months. We host it.

Who it is for

Teams that have an urgent, recurring workflow for publishing or finding spatial data and a clear reason to address it now. We look for a committed champion, users who can try the workflow, a first dataset you have the right to host, and a plausible buying or procurement path if the pilot succeeds. Organization size and geography are not selection requirements. A useful first outcome might be finding a known dataset faster, publishing a layer with a shareable map, or completing a repeatable QGIS/OGC workflow.

Not a fit: sensitive or regulated data such as personal health, criminal justice, or export-controlled records, or safety-critical and emergency workflows. A standard vendor or security review is welcome as part of fit assessment; we will confirm whether the agreed hosting setup can meet its requirements before any upload. The self-hosted edition (opens in a new tab) is available, but self-hosting alone does not make GeoLens suitable for sensitive or safety-critical use.

How it works

1. 1

   Apply

   Use the short form below. Priority and waitlist handling depend on when you apply; the current application status appears above the form.

2. 2

   Confirm fit and outcomes

   A 20–30 minute call covers the recurring workflow, current workaround, intended users, first dataset, a measurable outcome, and your buying or procurement path.

3. 3

   Agree the pilot plan

   The signed agreement records a kickoff date, the exact planned calendar dates for the four-month term, an activation deadline within 30 days of kickoff, the data and usage scope, hosting details, support expectations, an export and retention plan, and indicative paid continuation terms.

4. 4

   Onboard and activate

   We help load the first dataset and complete the agreed workflow for its intended users. The target is activation within 14 days of kickoff and the firm deadline is no later than 30 days after kickoff. Activation means the dataset is loaded and the workflow is ready for its intended users; both sides confirm the actual date in writing. If the deadline is missed, we agree a dated extension or close the pilot.

5. 5

   Measure progress

   The four-month term begins on the mutually confirmed activation date; we confirm or amend its calendar start and end dates in writing then. We meet briefly every two weeks, with a day-30 activation review, day-60 progress review, and day-90 transition plan measured from activation. Either side can stop if the agreed outcome is not on track.

6. 6

   Plan the transition

   Choose a paid hosted continuation, a supported self-hosted handoff, or closure. If you want to continue on hosted terms, we agree the final quote no later than 30 days before the written end date.

Plain facts

• GeoLens is open source under the Apache 2.0 license. The pilot is a hosted service; a move to self-hosting needs an agreed handoff plan and may require work beyond file or API exports.
• You retain rights to your data. Before onboarding, we agree the export and handoff scope, timing, assistance, and retention and deletion schedule, including backup retention.
• Support is founder-led; the agreement states the contact and expected availability for this cohort. There is no uptime SLA.
• We do not have third-party security attestations such as SOC 2. We can discuss standard review requirements before onboarding.
• Continuing on hosted terms is paid and optional. We discuss indicative terms or a quote before the pilot agreement.
• The pilot is run by Carto Concepts, LLC, the company behind GeoLens. We can offer the hosted pilot only where US sanctions and export rules allow it, which is why the form asks for your country.