Let your workflows thrive, grow, and adapt with AIP.
Watch as Palantir Group Lead Xinyi Wang takes us through the full-spectrum toolchain required to rapidly iterate on mission-critical workflows.
These builders, you know that your application building doesn't stop when you have your first set of users. You have bugs to fix, you have features to add, maybe even have migrations to run. How do you do all of that without disrupting your users or compromising the stability of your production workflows? So we see workflow building as a journey through several different levels. I'm gonna call it out up front that you don't have to go through all the levels. We've seen plenty of incredibly impactful workflows at Zero and One, but we just want to show you what is possible within the platform today. So let's walk through this journey together. Starting at level 0, you just have one production environment and you're making edits straight and broad. You don't have users yet and you're just trying to move fast, break things and get it done. This is probably what you'll be doing in the hackathon and or in the pilot phases of your projects. Now moving on to level 1, you still have one production environment, but you're using branching to manage your changes. Maybe because you want more stability or maybe because you have more devs working together. Branching comes very naturally to doves. When you create a branch you get a mini environment to yourself and you can make cross cutting changes across pipeline, ontology, workshop, and has all of them reviewed and tested by someone else before you merge it into your production environment at once. Now, moving beyond branching to level 2, you start seeing more separation between dev and prod. You set up different environments and you use DevOps to promote releases between them. This is useful if you want to dev against different data sources or if you want isolated test environments. It is more maintenance and setup than just using branching alone, but it gives you an additional level of stability and release management for your workflows that needed. And finally, on to Level 3, product delivery. Instead of just going from dev to prod, you now have many production environments. You're not just building a workflow, you are delivering a product to multiple customers. So traditionally we've thought about software development as applications and services written in code. But when you're building in Foundry, you are also building software, you are encoding business logic, you are automating processes, and you're delivering value just like any other coded application. And so in Level 3, we're building the infrastructure that lets you distribute and deploy your workflows into multiple production environments like any other software. Product.
Workflows thrive only when oversight keeps pace with automation.
AIP accelerates iteration, but speed without transparency turns “mission-critical” into “no-appeal.”
If you have built or deployed these pipelines and have seen risk scores drive action without review, I need to understand where the guardrails fail.
Signal: https://signal.me/#eu/GYcRJD6IDdZWeMgdodM0ElLSFDoE-1ORex-M9iVCYVo40wdn1N1Jp5ks8yt0-CFn
Proton: bigbirdreturns@proton.me
Predictive Strategic Analysis | Silent Canyon Architect
1wWorkflows thrive only when oversight keeps pace with automation. AIP accelerates iteration, but speed without transparency turns “mission-critical” into “no-appeal.” If you have built or deployed these pipelines and have seen risk scores drive action without review, I need to understand where the guardrails fail. Signal: https://signal.me/#eu/GYcRJD6IDdZWeMgdodM0ElLSFDoE-1ORex-M9iVCYVo40wdn1N1Jp5ks8yt0-CFn Proton: bigbirdreturns@proton.me