Flexible options to scale with you

Frequently asked questions

• What is OpenFn?

  OpenFn is the leading Digital Public Good for workflow automation. It’s fully open source software that enables users to quickly build automation and data integration solutions, securely run and monitor them via a central administrator console and audit trail, and flexibly scale on hosted or local deployments. OpenFn is trusted by NGOs and governments in 40+ countries to deliver more efficient health and humanitarian care through automation.

  OpenFn is also sometimes classified as an “integration platform” or “iPaaS” (integration platform-as-a-service), “middleware”, “interoperability layer”, and/or tool for “ETL” (extract, tranform, load).

  OpenFn is a recognized Digital Public Good, Global Good for Health, and OpenHIE-compliant workflow engine. Check out OpenFn Documentation and Community to learn more.

• What apps can OpenFn integrate with?

  OpenFn can integrate with any app. OpenFn provides 70+ “adaptors”—free and open-source (FOSS) connectors that make it easier to achieve interoperability between the most in-demand software in the LMIC government and NGO space. Lots of these are for established Digital Public Goods (DHIS2, OpenMRS, CommCare, Kobo Toolbox, OpenHIM, RapidPro, &c.) but OpenFn also provides adaptors for non-sector-specific technologies like Salesforce, Twilio, SQL/NoSQL databases, as well as any REST API.

  OpenFn can connect to any system via HTTP, but our community has also built dozens of adaptors to save time and money while connecting to most commonly used systems. You can even extract raw data files, or even run web scraping or browser automation tools with OpenFn.

  Developers can also extend or [build their own] custom adaptors for their own applications to fast-track integration setup and to securely handle authentication.

• What is a workflow?

  Workflows are automated processes or sets of instructions that accomplish a task. In OpenFn, all workflows have a Trigger (something that starts them), various Steps (the individual actions that are performed automatically), and Paths that define the automation logic (as in, “Follow this path if patient data is incomplete”).

• Do I need to know how to code?

  Simple workflows can be configured without code using OpenFn’s workflow builder. However, complex workflows that involve data transformation steps will require JavaScript and/or SQL. See OpenFn Docs to learn more, or contact us if you need help finding a developer to support your implementation.

  OpenFn provides a low-code visual interface for configuring automated workflows. Depending on the apps you are connecting with, specific OpenFn Adaptors (or “connectors”) may offer additional clicks-only configuration option. This means that most users can successfully configure a basic workflow on OpenFn. Then, if data engineering is needed for a specific workflow step (e.g., to re-format or transform data, to perform calculations, to loop or iterate a subprocess), then JavaScript is the primary programming language used in OpenFn.

• Is OpenFn open source?

  Yes. OpenFn is free and open source software, but requires resources to implement and maintain it.

  You can implement OpenFn on your own, using the open-source deployment tools, documentation, and Community forum. See Github for more.

  If you seek expert help or want to pilot your automation quickly, OpenFn offers a secure, cloud-hosted offering, as well as direct implementation and support services. See pricing page for more.

• How much does OpenFn cost?

  OpenFn is free and open source software, but requires resources to implement and maintain it.

  You can implement OpenFn on your own, using the open-source deployment tools, documentation, and Community forum. See Github for more.

  If you seek expert help or want to pilot your automation quickly, OpenFn offers a secure, cloud-hosted offering, as well as direct implementation and support services. See pricing page for more.

• How does OpenFn comply with data security policies?

  Yes, OpenFn can be configured to comply with your country- or organization-specific data security policies. At OpenFn, we prioritize Secure, Stable, and Scalable (“S³” is our mantra) solutions—in that order. We protect your data, maintain live integrations, and grow alongside your organization. Trusted by governments and NGOs worldwide, OpenFn offers:

  • Secure platform defaults to protect your data and minimize breaches
  • Robust, configurable security settings to ensure compliance with your policies
  • “Zero-persistence” data pipelines & local deployment options to fully control where data is stored
  • Security implementation training & guidance for your project teams

• How do I get help?

  For all users, OpenFn provides an open source Documentation site docs.openfn.org, Community forum community.openfn.org, as well as example work plans, checklists, & templates.

  If you’re seeking expert help, OpenFn’s core team also provides paid, direct implementation and support services, or can connect you to certified implementation partners in your region. Contact us to learn more.

• Where is OpenFn hosted?

  For organizations seeking to quickly implement solutions on the cloud, OpenFn provides a turnkey, hosted platform-as-a-service (SaaS on openfn.org). OpenFn’s cloud-hosted platform (see SaaS plans) is hosted on Google Cloud Platform U.S.-based servers. At an additional cost, OpenFn SaaS can also be made available in the country and cloud-hosting provider of your choice. Contact enterprise@openfn.org to learn more about our localized cloud-hosting offering.

  For organizations seeking to deploy OpenFn on local server infrastructure, OpenFn provides open-source deployment tools, as well as a managed deployment and support service, if seeking technical ssistance.

• How do I pick an OpenFn SaaS plan?

  OpenFn SaaS plans are primarily based on the following

  1. How many workflows do you want to automate?
  2. How often will these workflows execute?
  3. How much data will be handled by these workflows?

  Answers to these questions can help you determine the appropriate (1) number of workflows, (2) number of workflow runs per month (or per year), and (3) the type of workflow run needed (i.e., standard, batch, power). See pricing page for a detailed breakdown or contact us for a consultation.

• Can I deploy OpenFn on my own servers?

  Yes. OpenFn provides open-source deployment tools (see Github), as well as offers a paid deployment and support service, if you seek expert help getting started contact enterprise@openfn.org.

  See OpenFn Docs to learn more about the available deployment options and requirements.

  Many OpenFn customers seeking to prototype and pilot solutions often opt for a SaaS plan, before later migrating their solutions to local servers when ready to run at larger scale. Because of OpenFn’s portability specification and open-source deployment tools you can transition between these various pathways at any time. We’re committed to a no vendor lock-in experience.