Shipyard VS Apache Airflow

Shipyard's answer

Shipyard deploys in days, not weeks or months.

Shipyard is built for people of all technical backgrounds thanks to no code, open source low code, and full code options. Someone less technical, like a data analyst can deploy and build workflows with Shipyard just as easily as a data engineer who may choose to partially if not fully code within Shipyard.

Support is immediate. Our team is always available, as opposed to open source tools that primarily relies on communities for answers. The delay from the latter can prove to be an issue for many organizations.

You can test and deploy from your local environment in Shipyard, unlike all other orchestrators.

YAML configuration that syncs with drag and drop.

150 and counting open source low code blueprints allowing you to get started faster and not have to start from scratch.

Shipyard provides the infrastructure which allows for faster scaling, more elasticity, and a reduction in costs.

Shipyard's answer

Today our primary audience is data engineers, analytics engineers, data analysts, BI analysts, and heads of data/CDOs. We're currently a best fit for organizations with 500 of fewer employees, but by the end of Q1 2024 our primary audience will shift to large mid-market/small enterprises. We're product led growth on one hand, we offer a forever free trial, but we compliment it with a sales team to work with customers, which are primarily large, which want to work with a salesperson and other data experts.

Shipyard's answer

Lack of complexity, ease of use, and speed.

While just as powerful as any of our competitors, Shipyard is significantly easier to deploy, use, and to onboard others to Shipyard regardless of their technical background.

Shipyard is also significantly less expensive. Open source is free in that you don't have to pay to access the tools. But you do need the manpower and budget to code and built upon the open source to get the orchestration solution that is specific to the needs of your organizations.

You have a partner in Shipyard, one who's always available whether it's technical in nature or you just need to bounce ideas off or get another perspective from another data expert. We're strong believers in giving back to our data community and supporting our customers and partners, and you can always count on us exactly when you need us.

We're extraordinarily nimble. Whether you need a new integration, blue print, or other addition to satisfy your needs, we have the team to meet your needs, fast.

Shipyard's answer

• Apache Airflow
• Prefect
• Dagster
• Mage

Shipyard's answer

Our founding story aligns with our product philosophy. Our story is very much our strategy.

Our co-founder, Blake Burch, was a full-time data practitioner.

He had a love-hate relationships with low-code tools.

On the one hand, they made his life so much easier. Blake could click a few buttons and get access to data that he needed in five minutes instead of spending a week of work fiddling with new API endpoints.

On the other hand, using any of these tools meant that Blake had a few inevitable tradeoffs: - He always seemed to run into situations where the tool didn't support something that he needed for his specific use case. As a result, Blake would be stuck writing his own scripts that had to live on a separate platform, disconnected from his other solutions. This meant that Blake was then responsible for managing solutions across multiple tools. - If the low-code tool offered the ability to run code, it was always limited in some way. For some tools, you could only use pre-installed packages. For others, you were required to format the data in a very specific format. Some even restricted to small runtimes, small data, and small memory. - While the low-code tools were easy to use, the more Blake relied on them, the more of a black box his business' solutions became. Nobody knew exactly how they worked under the hood which created an extreme level of lock-in.

Blake and his co-founder, Eric Elsken, designed Shipyard to address these issues. Shipyard believes that low-code and your code should be able to work together seamlessly without any tradeoffs. To maximize your impact, data practitioners deserve a platform that affords them the flexibility to solve problems how they need. They have options.

That's why with Shipyard: - You can run your own Python, Node, or Bash code directly in the platform without any changes. There are no limitations on the script functionality that can be executed. - You can run our low-code Library Blueprints in the platform by providing a few simple inputs. These Blueprints are 100 percent open-source Python packages that you can dig into and even help contribute to. If you ever need to tweak the functionality - go for it. The code works outside of Shipyard too, so you can test and port the functionality as needed. - You can turn your own scripts into low-code Blueprints that look and feel exactly like our Library Blueprints. This is perfect for proprietary business logic that needs to be reusable by anyone in the organization.

In the ideal situation, a workflow should be a mixture of low-code solutions plus your own code when absolutely necessary.

You have more flexibility with Shipyard than any data orchestration tool that's ever been built.