Open your workspace
In Alteryx, workflows live as files (.yxmd, .yxzp) that execute locally or on Alteryx Server.
In Prophecy, projects are stored in Git and managed through branches, version history, and deployment workflows. Instead of sharing workflow files manually, teams collaborate through version-controlled project changes.
In Alteryx:
You open Designer, and load your .yxmd or .yxzp workflows from your local folder or a network drive.
In Prophecy:
You log into your Prophecy workspace in the browser. Pipelines, datasets, and configurations are stored in Git; you open your branch directly from the Prophecy interface.
Connect to data sources
In Alteryx, workflows often read directly from local files or shared folders. In Prophecy, you can still work with files such as CSV, Excel, JSON, and XML, but pipelines run directly in the target platform environment rather than on a local machine. The overall experience is similar: upload a file, configure the Source gem, and preview the data. However, files and connections live inside the workspace or cloud platform environment, allowing pipelines to run consistently across development, testing, and production deployments. In Alteryx: You drag an Input Data tool onto the canvas and either select a data file (such as CSV or Excel), or configure a database connection. In Prophecy: You add a Source gem to the visual canvas. You can upload CSV, JSON, text, Excel, and XML files and you can connect to other data sources through JDBC or a cloud connector (Snowflake, Redshift, Delta, and so on).Clean and transform data
Prophecy transformations compile into SQL operations that execute directly on the target platform. Performance, optimization, and scalability come from the underlying warehouse rather than from a separate ETL runtime. In Alteryx: You chain tools like Filter → Formula → Summarize, testing each with a Browse tool and re-running. In Prophecy: You build similar logical sequences using Filter, Aggregate, Reformat, and other gems. You can preview sample data for each gem using Propehecy’s Data Explorer.Test and debug
In Alteryx: You click “Run,” inspect intermediate results, adjust formulas, and rerun until satisfied. In Prophecy: Because pipelines execute directly in the target platform, testing in Prophecy more closely reflects production behavior. You can inspect warehouse execution plans, logs, and runtime metrics directly in the underlying platform.Documenting or sharing your work
In Alteryx: Documentation often lives in annotations or shared screenshots. In Prophecy: Prophecy projects include version history, deployment tracking, and Git-backed collaboration workflows. Teams can review changes visually or in generated SQL/Spark code before promoting projects into shared environments.Collaboration and review
In Alteryx: You might email.yxmd files or use Alteryx Server to share workflows. Version control is mostly manual.
In Prophecy:
All collaboration happens through Git, although Prophecy requires no knowledge of using Git directly. Prophecy coordinates pushing your branch and opening a pull request. Teammates can review changes visually and in code. This replaces shared folders with a formal, trackable workflow.
Monitor and troubleshoot
In Alteryx: If a job fails on Alteryx Server, you check logs in the Gallery or local output files. In Prophecy: You view run histories and logs in Prophecy, with full access to Spark logs, cluster metrics, and lineage tracking.Iterate and reuse work
In Alteryx: You might copy parts of workflows or create macros for reuse. In Prophecy: You can reuse transformations, configurations, and pipeline components across projects through shared gems, version-controlled code, and parameterized workflows. Because projects are stored in Git, teams can standardize and evolve reusable logic over time rather than duplicating workflow fragments manually.Save/commit work
In Alteryx: You save your workflow as a local.yxmd file or publish it to Alteryx Server.
In Prophecy:
Your work is version-controlled through Git. Prophecy manages commits, branches, and pull requests through the interface, so teams can review changes, track version history, and deploy projects through a consistent workflow without requiring direct Git commands.
Deploy and schedule
In Alteryx: You publish completed workflows to Alteryx Server or the Gallery to automate runs. Scheduling, credentials, and runtime settings are configured through the Server interface. Promotion between development, testing, and production environments often involves exporting and re-importing.yxzp workflow packages manually.
In Prophecy:
Prophecy separates project publication from deployment. You can publish reusable project versions, deploy those versions to development or production fabrics, and manage environment promotion through Git-backed workflows rather than manual package transfers. Scheduling and deployment settings are tied to the project, helping you create more consistent and auditable deployments across environments.