Product Updates

We just shipped something we should have shipped a long time ago: real documentation. If you've ever tried to use Skyvern and found yourself digging through GitHub issues, Discord threads, or old blog posts to figure out how something works, that's on us. We had the classic startup problem: we were shipping features faster than we could explain them. So we built skyvern.com/docs from the ground up. Not a README with some curl examples. Actual, structured documentation that covers everything fr

Automation pricing is usually optimized for the vendor, not the user. You pay per step, per action, per minute, or per obscure unit that only makes sense if you already understand the internals of the system. The result is predictable: people under-automate, over-optimize prematurely, or stop experimenting altogether because they don’t trust the bill. We’re changing that. Today we’re launching a new pricing model for Skyvern, designed around a single goal: make it obvious what automation cost

Most companies already know how their work gets done. It’s written down somewhere: * internal SOPs * runbooks * onboarding docs * Notion pages no one wants to maintain The problem isn’t lack of documentation. It’s that documentation doesn’t run. Today we’re shipping SOP Upload, a way to turn existing process documentation directly into executable browser automation. The gap between “written” and “working” Traditional automation tools assume you’ll start from scratch: * re-specify t

We just shipped something we should have shipped a long time ago: real documentation. If you've ever tried to use Skyvern and found yourself digging through GitHub issues, Discord threads, or old blog posts to figure out how something works, that's on us. We had the classic startup problem: we were shipping features faster than we could explain them. So we built skyvern.com/docs from the ground up. Not a README with some curl examples. Actual, structured documentation that covers everything fr

Automation pricing is usually optimized for the vendor, not the user. You pay per step, per action, per minute, or per obscure unit that only makes sense if you already understand the internals of the system. The result is predictable: people under-automate, over-optimize prematurely, or stop experimenting altogether because they don’t trust the bill. We’re changing that. Today we’re launching a new pricing model for Skyvern, designed around a single goal: make it obvious what automation cost

Most companies already know how their work gets done. It’s written down somewhere: * internal SOPs * runbooks * onboarding docs * Notion pages no one wants to maintain The problem isn’t lack of documentation. It’s that documentation doesn’t run. Today we’re shipping SOP Upload, a way to turn existing process documentation directly into executable browser automation. The gap between “written” and “working” Traditional automation tools assume you’ll start from scratch: * re-specify t

Most browser automation fails because the interface between humans and automation is wrong. We ask users to describe workflows that are fundamentally visual and stateful. Then we’re surprised when the agent breaks, edge cases pile up, and maintenance cost dominates everything else. We built the Skyvern Screen Recorder to change that interface. Instead of telling an agent what to do, you show it. Give it a try here: app.skyvern.com The core idea If a human can complete a workflow in a brow

Skyvern SDK v1+ lets you run tasks and workflows and share browser state over a CDP connection. The SDK supports two modes: embedded (local) and remote (cloud). Embedded (Local) mode Get started locally: * uv venv && source .venv/bin/activate — optional but recommended to create a virtual env * uv pip install skyvern — install the Skyvern SDK * skyvern quickstart — follow prompts to configure the environment (AI API keys, etc.) Python example: import asyncio from skyvern import Skyver

Automation Copilot reduces time-to-automation. Not by making automation “easier to start,” but by making it faster to: * build * modify * and maintain real, production browser workflows. What it is Automation Copilot is an in-product, workflow-aware chat interface. It can: * generate new Skyvern workflows from prompts * edit existing workflows in place * reason about failures and apply targeted fixes It operates directly on Skyvern’s workflow graph. Outputs are executable, not sugg

Skyvern’s open source project just got faster. 🚀 We’ve swapped out Poetry for uv — the blazing-fast new Python package manager. That means your builds are now: * Much quicker — installs and resolves dependencies in a fraction of the time. * Simpler — no more waiting around for environments to set up. * Future-proof — leveraging modern tooling to keep the developer experience smooth. What this means for you 1. Clone and build Skyvern like before — only now it’s way faster. 2. Contribu

Skyvern’s new Sequential Runs feature makes sure your workflows play nicely together — no more parallel runs stepping on each other’s toes or logging you out unexpectedly. This builds on our mission to make automated browsing reliable at scale, especially when authentication or session-sensitive sites are involved. Here’s what it unlocks: * Session-safe execution — runs now queue up and execute one after the other, so you never lose your login mid-workflow. * Predictable automation — no mor

I bet you thought our launch week was over last week? Well you’re wrong! Skyvern’s Azure Key Vault integration lets you authenticate into websites while keeping credentials locked away in Microsoft’s secure vault service. No hardcoded passwords, no local secret sprawl — just seamless, enterprise-grade security. This joins the family alongside Bitwarden and 1Password, giving teams flexibility to manage secrets with the provider that fits their stack best. This unlocks a whole new category of

One of the most common requests we’ve heard: “Can Skyvern pick up where it left off?” Until now, every run started fresh—like opening a brand new browser window each time. Clean, but sometimes too clean. Why Browser Sessions? Skyvern Browser Sessions prop up a browser and let you persist the real-time state of the browser This unlocks a whole new category of workflows where context matters: * Deploy code straight into the browser — combine AI navigations and trusty ‘ol code by CDPing int

Never lose your favourite workflow setup again! When you’re building workflows, it’s easy to accidentally overwrite a prompt that was working beautifully—or remove a configuration you loved while experimenting with new ones. Until now, once those changes were made, they were gone for good. With Version History, you can now browse through past versions of any workflow and restore the exact setup you want. This makes iterating safer, faster, and way less stressful. How it works * Build your

Running workflows end-to-end makes testing difficult! While autonomy is perfect for B2B workflows in production, when you’re designing a new workflow, it makes testing slow and frustrating. Now, with Debugger, you can run a single block at a time, inspect, tweak, and rerun again—all within the workflow editor How it works * Go to the workflow — a browser will load up right where you need it: in the editor. You will see the play icon next to every block and a browser spinning up on the right

Ask and you shall receive 🤑 We heard you: Skyvern was too pricey! So we went back to the drawing board and found a way to bring costs down. 🚀 From now on, Skyvern steps are 50% cheaper! What changed? 10¢ → 5¢ per step A step = anytime Skyvern visits or scans a page That’s the heartbeat of your automation—every scan, every map, every action. And now, it costs half as much. Which means your automation dollar goes twice as far. Why we’re doing this We’re starting off launch week with a

🚨 May I have your attention, please! Our most complex feature, ForLoops, got a massive upgrade today If you’ve ever tried to set up a loop in Skyvern before, you know the drill: carefully define the structure, make sure your variables are just so, and pray you didn’t miss a bracket somewhere. It worked and it worked well, but troubleshooting often required coffee, tears, and a minor sacrifice to the debugging gods. Introducing 🥁 Natural Language Loop Values 🥁 Now, you can just say what y

We're integrated with N8N (Again!) You've seen this announcement once before This time, the Skyvern node is a verified node that you can access via n8n cloud :) n8n is a workflow automation platform that empowers technical teams to build complex, multi-step workflows using their 400+ native integrations. Why Integrate into n8n? There has been a lot of overlap between Skyvern users and n8n users. So, we’ve made an integration that connects the two more easily. Here’s what we know: people of