IP Inlay for FileMaker

Pricing

Licensing for FileMaker teams, consultants, and production rollouts.

Start with an evaluation, move to a team deployment, or scope enterprise licensing when you need broader rollout, procurement support, or custom work. Exact pricing is quoted based on deployment shape rather than hidden behind vague tiers.

Fast Start

Evaluation

Best for developers qualifying Inlay against a real FileMaker workflow before committing to a wider rollout.

Commercial fit

Pilot or proof of concept

Best fit
Consultants and internal developers
Goal
Validate the workflow quickly
  • Short path to testing S3, media, diagnostics, or timecode use cases
  • Guidance on compatibility, install steps, and release selection
  • Clear handoff path into production licensing if the pilot succeeds
Ask about an evaluation

Production

Team Deployment

For active solutions where a FileMaker team needs predictable licensing, seat-aware activation, and a stable release path.

Commercial fit

Department or small team rollout

Best fit
Production FileMaker solutions
Goal
Reliable deployment and support
  • Release-aware downloads and deployment coordination
  • Seat-aware activations tied to the owning organization
  • Support for rollout, updates, and machine moves
Talk about a team rollout

Scale

Enterprise

For larger organizations that need procurement alignment, broader deployment controls, and direct coordination on activation, support, and rollout policy.

Commercial fit

Multi-team or regulated environments

  • Procurement-friendly annual planning and licensing discussions
  • Activation and support expectations aligned to production operations
  • Coordination on release policy, deployment timing, and admin workflows
Talk about enterprise licensing

Extension

Custom Work

When a production FileMaker workflow needs a capability beyond the standard catalog, Inlay can also carry customer-specific functions and integrations.

Commercial fit

Specialized workflows

  • Feature scoping based on your existing FileMaker workflow
  • Licensing and entitlement model aligned to the delivered function set
  • Clear path from request to implementation and rollout
Scope custom work

What stays consistent

Every commercial path uses the same deployment foundation.

Whether you are validating a pilot or rolling out broadly, the operational model stays the same: versioned releases, signed license artifacts, seat-aware activations, and organization-level ownership of the deployment.

  • Organization-based entitlements
  • Seat-aware activation enforcement
  • Signed license artifacts for deployed systems
  • Versioned docs and release history for controlled upgrades