Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

FME Data Virtualization review

#25 of 27 in Geo Tools

A managed way to expose FME workspace data through configurable REST endpoints.

6.8/10Editor score
FME Data Virtualization6.8 Visit Safe Software

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

FME Data Virtualization is a capability of the FME Platform for data teams that need to expose data through REST APIs backed by FME workspaces. It can serve applications, dashboards, and other consumers, with workspaces defining the responses. The fit is strongest for mid-market and enterprise teams already working with FME that want to manage API access and behavior rather than build separate integration infrastructure. It is an API-focused tool, not an offline mapping or core spatial-analysis product.

The endpoint configuration covers GET, POST, PUT, and DELETE methods, along with API- and endpoint-level authentication and access permissions. Teams can define reusable JSON request and response schemas, cache GET responses with a configured time to live, and return asynchronous responses with callback processing. OpenAPI specifications can be imported and exported, and users can test endpoints and view generated API documentation. Workspace responses are authored in FME Form and published to FME Flow, making the FME environment central to the workflow. Deployment options include cloud and self-hosted.

According to Safe Software's pricing page, pricing is tailored to each client and prospective buyers are directed to sales; no public price is given for Data Virtualization. Documentation is the listed support channel. Choose it when controlled, documented REST access to FME workspace processes is the requirement, particularly where methods, schemas, and asynchronous handling matter. Teams seeking mapping features, offline maps, or a standalone way to build APIs without the FME workspace workflow should look elsewhere.

FME Data Virtualization pros and cons

  • Where it wins
    • Creates OpenAPI-compliant APIs from FME workspaces
    • Supports GET, POST, PUT, and DELETE with access controls
    • Includes schemas, caching, callbacks, and API documentation
  • Where it doesn't
    • Requires FME Form and FME Flow to author and publish workspace responses
    • Pricing is tailored and requires contacting sales
    • Focused on API exposure, not offline mapping or spatial analysis

FME Data Virtualization fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update