Isolated by default. Portable by design.

One dedicated database per tenant, the same binaries on any cloud, and a platform you can provision, monitor and audit.

The tenancy model

Platform operations

Provisioning, monitoring and upgrades, run by Invasystems

Per-tenant data plane

One dedicated database per tenant.NET Core services and workersRedisObject storageERP adapter

Surfaces

Angular web app and PWAField app (offline)

What that gives you

Tenancy model

No cross-tenant tables or foreign keys; tenant binding at request time; per-tenant storage and backups.

Cloud-portable

Identical binaries on AWS, Azure, GCP or on-premise; a standard SQL database and S3-compatible storage; no vendor SDKs in business logic.

Reliability

Tier SLAs of 99.9% and 99.95%, defined RPO and RTO, and graceful degradation when an ERP or queue is down.

Scale

Hundreds of tenants, thousands of users each, millions of transactions a year, with ring and canary migrations.

Onboarding and lifecycle

Sandbox-first onboarding, your choice of region, and a smooth path from trial to production, managed for you.

Operated for you

We provision, monitor and upgrade the platform, and watch health, integrations and capacity so issues are caught early.

How it is built

Modern and portable: the same binaries run on any cloud or on-premise, and Invasystems provisions, monitors and upgrades the platform for you.

  • Angular web + PWA
  • .NET Core services
  • SQL database
  • Redis
  • S3-compatible storage
  • Message queue

Frequently asked questions

Where does our data live?

In your own dedicated database, one per tenant, in your chosen region, with in-region backups by default.

Can we run on our own cloud or on-premise?

Yes. The same binaries run on AWS, Azure, GCP or on-premise, using a standard SQL database and S3-compatible storage with no vendor SDKs in business logic.

What happens if our ERP or the message queue is down?

FieldDNA keeps operating and degrades gracefully, then reconciles when the dependency returns.

How do you handle schema upgrades?

Through ring and canary migrations, so changes roll out progressively rather than all at once.

Ready to run your distribution chain from one platform?

Live walkthrough on Microsoft Teams · Tailored to your distribution model · Works on web, Android and iOS