SECURITY & DEPLOYMENT

Built for teams who answer to bank auditors.

Run Fieldor in our cloud, in yours, or inside your own data centre. Every change is logged, every user sees only their sites, and every photo carries proof of where it was taken.

Request the security pack
AUDIT LOG · INC-118204IMMUTABLE
14:02:13system created incident from switch feed
14:02:14planner assigned S. Rao (6.2 km)
14:41:07S. Rao arrived · geofence 18 m · device verified
15:12:40S. Rao uploaded 4 photos · hashes sealed
15:20:02R. Menon changed SLA reason · approval required
15:31:55S. Rao closed · client notified
DEPLOYMENT

Where your data lives is your call.

01

Fieldor Cloud

Live in weeks. Hosted in-region on Azure, managed and monitored by us.

  • India and EU regions
  • 99.9% uptime commitment
  • Daily encrypted backups
02

Your private cloud

A dedicated instance in your cloud tenancy, under your keys and policies.

  • Your subscription, your network rules
  • Bring your own keys
  • We operate it, you own it
03

On-premises

Inside your data centre, sized to your sites, users and daily ticket volume.

  • Sized for 50,000+ sites
  • Integrates inside your perimeter
  • Phased go-live with rollback plan
ACCESS

People see only their sites.

Role- and site-based access for every user, partner and client login. SSO with SAML or OIDC, enforced MFA, session limits.

AUDIT TRAIL

Every change, on the record.

Who changed what, when and from where — kept for the life of the contract and exportable for your auditors.

EVIDENCE

Photos that can't be swapped.

In-app capture only, stamped with site, coordinates and time, sealed with a hash on upload. Gallery uploads are refused.

FIELD DEVICES

One engineer, one device.

Device binding, mock-location detection and remote sign-out when a phone goes missing.

ENCRYPTION

In transit and at rest.

TLS 1.2+ everywhere, AES-256 for data at rest, secrets in a managed vault.

TESTING

Tested by people paid to break it.

Independent VAPT twice a year; summary reports shared under NDA.

MOVING FROM A LEGACY SYSTEM

No big-bang switch-overs.

Closely linked modules move together; the rest follow once those are stable. A rollback path is kept ready for anything that can't be fixed inside the go-live window.

  1. WEEK 0–2Discover. Sites, assets, users and integrations mapped; data cleaned.
  2. WEEK 3–6Pilot. One zone live, side by side with the old system.
  3. WEEK 7–12Roll out. Zone by zone, with a forward-deployed engineer on hand.
  4. +90 DAYSStabilise. Next modules move only after a 90-day cooling period.