Skip to main content

🏢 Geoflip for Enterprise

Geoflip is fully deployable into your own infrastructure so you keep full control of data, security, and scale. The code is licensed under Apache-2.0; there is no enterprise license fee to self-host. If you want help operating at scale, Intelligis can offer commercial support.

💡 Why self-host Geoflip?​

While the public API at https://api.geoflip.io is free and convenient for testing and low-risk workflows, some organisations need:

  • Data sovereignty to keep inputs, outputs, and logs within your network or VPC
  • Security and compliance alignment with your IAM, logging, retention, and audit policies
  • Operational control to tune resources, autoscaling, and job queues to your SLAs

Self-hosting Geoflip addresses all of the above.

🔎 Deployment​

  • Backend API and workers
    Runs inside your environment. The repository includes a docker compose configuration that provisions the API along with its dependencies such as Redis and Postgres. Use this to stand up the backend and integrate it with your storage, message broker, and observability stack.

  • Frontend web app
    The web UI is a React single-page application. It is not bundled into the provided docker compose file, but it is straightforward to deploy separately as a static site. Build the frontend and host the compiled assets on your chosen platform, then point it at your API endpoint.

Common frontend hosting options include:

  • Any static web server such as Nginx or Apache
  • Object storage with CDN such as S3 and CloudFront
  • Modern hosts such as Vercel or Netlify
  • Traditional VM or container with a static file server

During frontend deployment, configure the API base URL in the frontend environment so the UI talks to your self-hosted API.

If you would like early guidance on wiring the UI to your backend, contact [email protected] or refer to the README files in the geoflip repo on github

🔁 Feature parity with the hosted API​

Self-hosted Geoflip exposes the same API schema as the public service at api.geoflip.io, so integrations move across with minimal changes.

  • Readers and writers for common spatial formats such as GeoJSON, SHP, DXF, and GPKG
  • Transformations including buffer and union, with reprojection via an output CRS
  • Asynchronous jobs with polling endpoints for status and results
  • No enforced public quotas; you set concurrency, limits, and retention

For the up-to-date list, see the Readers, Writers, and Transformations sections.

🧱 Reference architecture (high-level)​

Inside your network or VPC, you would typically run:

  • An ingress or reverse proxy and optional SSO or identity gateway
  • Geoflip API service
  • Geoflip worker processes
  • A message broker such as Redis or RabbitMQ
  • Storage for temporary inputs and outputs such as local persistent volumes or an S3-compatible object store
  • Optional static hosting for the React frontend aligned to your API base URL

You own scaling, logging, monitoring, backup and retention, and security controls.

🔐 Security and data handling (self-host)​

  • Inputs and outputs remain inside your infrastructure
  • Configure retention windows to automatically delete outputs after your chosen period
  • Integrate with your SIEM and audit pipelines
  • Optionally front the API with your SSO or IAM and network controls

✅ Use cases​

  • Sectors with strict compliance such as defence, mining, utilities, government, and finance
  • Automated pipelines processing sensitive geospatial data
  • Disconnected, air-gapped, or remote environments

🗺️ Roadmap highlights​

  • Consolidated examples for deploying the frontend alongside the backend
  • End-to-end deployment guide for common platforms

🤝 Support options​

Need help getting set up? Intelligis can support you and your business with implementation and commercial support.

[email protected]

▶ Next steps​

  1. Review the API in Getting Started at /getting-started
  2. Plan deployment: choose infrastructure for broker, storage, and observability
  3. Deploy the frontend as a static site and set the API base URL to your backend
  4. Align retention and access controls with your security policies
  5. Contact us if you need managed hosting or early self-host guidance: [email protected]

Summary​

  • Open-source geoprocessing you can run anywhere
  • Same API as the hosted service, with your controls and policies
  • Frontend deployable as a separate React static site
  • Optional managed hosting and support from Intelligis