Lyhnidos Geo
Plans and pricing
Every plan runs the same engine: maps and data that remember how places change over time, links that work in ArcGIS and other map tools, access for AI assistants, and the Studio. What changes is how many databases a workspace may hold, how many spatial queries it may run in a month, and how much it may store.
Choose for the work you need to do
Start with one representative dataset and follow it from import to a saved result. The plan allowances above come from this installation. Source formats, file sizes and processing limits also depend on the operation you choose.
- Prepare a file: review its fields and types, preview the transformation, then check the complete-run limit. A successful sample does not prove that the full file fits.
- Repeat a workflow: allow storage for source tables, outputs and retained run history. Review the server’s scheduling support and how a failed run can be retried.
- Build an application: consider stored data, query usage and application-user allowances where offered. Configure sign-in, allowed origins and row access separately.
Before moving a large or business-critical workflow, verify its formats, largest expected input, runtime, recovery and required support with the actual deployment. A higher plan allowance does not remove an operation’s limits or imply an SLA.
Prices are shown in the currency this installation bills in and are charged by Stripe. Allowances are measured per workspace, per calendar month, and reset on the first of the next one.
Storage is measured as it is held rather than counted per month. Where a plan lists a ceiling above the storage it includes, what is held between the two is billed by the gigabyte for each month it is held; at the ceiling, new pages stop being allocated.