Plans & Pricing

A 24-hour target response on business days, on every plan. Our team works in Australia, in the AET time zone, which is the same working day as most of the people who write to us. Response time is not a premium tier here.

Fieldmark supports sign in with Google, with the Australian Access Federation (AAF), and with a Fieldmark username and password out of the box. Enterprise deployments can use other single sign-on configurations, including Okta, OIDC, and SAML.

Fieldmark is hosted in your preferred zone on DigitalOcean (e.g., Australia for Australian clients). Where a client requires it, we can deploy on AWS instead (may affect costs and default storage limits).

If sovereignty or internal policy means the system has to run inside your estate, Enterprise can be installed on your cloud or your own servers, and we support it there.

Invoicing, annual in advance, purchase orders accepted. Enterprise agreements are scoped to requirements: hosting model, support level, onboarding, and any custom branding.

We have prepared a HECVAT, the higher education sector's standard security questionnaire for vendors, and supplied it to enterprise clients during procurement review.

Independent penetration testing, data handling, and hosting details are set out on the security page.

Fieldmark is built on FAIMS3, an open-source platform you can host and operate yourself if you have the infrastructure and the expertise: github.com/FAIMS/FAIMS3. A Fieldmark plan buys hosting, the published mobile apps, support against a response target, and the team's time.

Two different answers, and the difference is who answers when it breaks. Self-hosted Enterprise puts the system on your infrastructure with our team supporting it, under an Enterprise agreement. Running the upstream FAIMS3 platform yourself is free and community-supported, but the operational work is yours.

You export it and go. Export is available at any time from the notebook's Export tab, in open formats including CSV and JSON, during an evaluation or on a paid plan.

Yes. Google and AAF, the Australian Access Federation, on the standard service (including individual and team plans), alongside sign in with a Fieldmark username and password. Okta is integrated and running in production for a current deployment, and can be configured for any enterprise deployment. Other SSO integrations are possible, including OIDC and SAML; tell us which provider your institution uses and we can incorporate that into your enterprise deployment.

In the DigitalOcean zone of your choice (e.g., in Australia for Australian deployments). Enterprise clients who require it can have Fieldmark deployed on AWS instead (may affect costs and default storage limits), and self-hosted Enterprise runs wherever your infrastructure is.

Enterprise agreements are scoped to requirements: hosting model, support level, onboarding, and customisation. To get a figure for your situation, talk to us.

Team subscriptions stack. A group that has outgrown one Team, but does not yet need an Enterprise agreement, can hold two or three Team subscriptions instead. Tell us how many devices and how much storage the work needs, and we will help you find an arrangement that fits.

Custom branding is an Enterprise capability: your logo, your colours, and possibly an app published under your own name, running the standard Fieldmark product. A custom application is a software development engagement, where we build capability Fieldmark does not have out of the box, as a standalone system on the infrastructure of your choice.

By invoice, annual in advance. Purchase orders are accepted, and we raise invoices to suit your finance system's requirements. Recurring monthly billing is available for individual and team accounts.