Oxflow FAQ

What if our systems do not have APIs?

Our service does not work with systems that do not have an API.

Do you have a Service Level Agreement (SLA) and uptime commitment?

Yes. We provide 95% uptime on the OxFlow services. We provide a four hour response time for new issues, during business hours: 8am to 5pm… Read More »

Is this service proprietary?

Yes and no. Our methods, change management system and team are the only proprietary aspects to our service. The core Apache-Airflow server is an open-source… Read More »

Does the service have a backup system?

Yes. We have two methods for backup: Our servers house no client data, so the only things needing backup are code and log files.

Are your services Cloud based?

Yes. We host our Airflow servers at a top tier virtual server service located in Northern California and Virginia.

Is Apache Airflow supported actively?

Yes. Apache Airflow is a very large open source community and is very actively supported and updated. Find more details here and here. We have worked in open… Read More »

Does your service include a Snowflake instance?

No. We walk the client through setup of a Snowflake account then we install our Data Mark footprint (see Terminology section). Costs for the Snowflake… Read More »

What if we already have Snowflake?

We always provision a new, isolated instance of Snowflake for our OxFlow service to ensure proper serviceability by our team and also protect any incumbent… Read More »

Is the OxFlow service a middleware product?

Yes. It is a set of tools that approximates a middleware tool. Our service is a combination of hosted Apache-Airflow, Github code repository and a… Read More »

How do you connect the Airflow system to our systems?

We ask our clients to provision a unique, non-shared user account for the Airflow Service to use on each system we are working with. Here… Read More »