Serverless Framework is a powerful deployment tool. But when it comes to locally developing, testing, and debugging Step Functions workflows, it was never designed for that job. Here's an honest comparison of what each tool does and why they're solving different problems.
Serverless Framework is a deployment and infrastructure-as-code tool. Thrubit is a local development environment built from the ground up for Step Functions. They're not the same category of tool you see the visual debugger, that becomes obvious.
serverless-step-functions plugin with limited debugging support.An honest look at what each tool supports for Step Functions development. Blue cells indicate Thrubit has a clear advantage for local workflow development.
| Feature |
Thrubit
|
Serverless Framework
|
|---|
| Primary Purpose | ||
| Primary use case |
Local Step Functions developmentRun, test, and debug state machines on your machine before you ever deploy.
|
Deployment & IaCDefine and deploy serverless infrastructure to AWS and other clouds. Local dev is a secondary capability via plugins.
|
| Step Functions focus |
Step Functions is the entire product — every feature is designed around it
|
Supported via
serverless-step-functions community plugin — not a core feature |
| Setup & Installation | ||
| Installation |
Download the desktop appDouble-click to open. Ready in under 2 minutes.
|
npm install + plugin setupInstall Node.js, Serverless Framework, configure
serverless.yml, add and configure plugins for local Step Functions emulation. |
| Configuration to run first workflow |
Point at your project folder. Done. Auto-discovery handles the rest.
|
Define state machines in
serverless.yml, configure plugin, wire Lambda functions — then run sls offline start |
| AWS credentials required for local dev |
No AWS account needed to run workflows locally
|
Required for deployment; local offline mode works without credentials for Lambda/Step Functions emulation
|
| Step Functions Support | ||
| ASL execution (local) |
Full Standard & Express supportAll state types: Task, Wait, Choice, Parallel, Map, Pass, Succeed, Fail, Catch, Retry
|
Via community pluginThe
serverless-step-functions plugin supports common state types; complex workflows may have gaps |
| Visual state machine debugger |
Built-in, real-timeWatch execution flow live on a visual graph. Click any state to inspect inputs, outputs, errors, and timing.
|
None — console log output only. No visual execution graph.
|
| Real-time execution tracing |
Step-by-step trace with timing, I/O, and state transitions as they happen
|
Terminal output only — no structured per-state tracing for Step Functions
|
| 60+ prebuilt workflow examples |
Healthcare, fintech, logistics, AI, aerospace, e-commerce — ready to run locally on day one
|
No included Step Functions workflow library — you write the ASL from scratch
|
| Lambda Execution | ||
| Local Lambda execution |
Real code, instant executionYour actual Lambda code runs directly on your machine — no container, no emulation layer, no spin-up delay.
|
Via serverless-offline pluginRuns a local HTTP server that emulates Lambda. Works well for API Gateway-triggered functions; Step Functions invocations require additional wiring.
|
| SAM template.yaml auto-discovery |
Point at your SAM project; all Lambda functions auto-discovered with no config required
|
Uses its own
serverless.yml format — SAM projects require migration or parallel config files |
| Lambda environment variables |
Loaded from your project's env files or SAM template automatically
|
Configured in
serverless.yml or via .env files with the dotenv plugin |
| AWS Service Mocking | ||
| Amazon Bedrock mock |
10+ model families built inClaude, Titan, Llama, Mistral, Nova & more — correctly-shaped responses at zero cost
|
Not available — your Lambda must call real Bedrock or you write your own mock
|
| SQS, EventBridge integration |
Local SQS and EventBridge for Step Functions direct integrations
|
Available via serverless-offline and companion plugins (serverless-offline-sqs, etc.) — requires additional setup
|
| Developer Experience | ||
| Native desktop app |
macOS + Windows native app — no terminal required to run workflows
|
CLI-only — everything runs in your terminal via
sls offline start |
| Open source |
Commercial product — free trial, paid license
|
Open source core (MIT). Serverless Framework Pro/Cloud features are paid.
|
| Pricing for local dev use |
Free trial, flat per-developer licenseNo usage-based billing, no surprise costs, no feature tiers for core Step Functions features.
|
Free for local development use. Paid plans apply only to cloud dashboard features.
|
Serverless Framework is excellent at what it does; deploying infrastructure. But Step Functions development requires a different kind of tool, and these are the areas where that gap is most visible.
serverless.yml or migrate your existing project. Just point Thrubit at your code and it figures out the rest.serverless.yml — which means maintaining a parallel config if you use SAM or CDK.serverless.yml and write your own state machine definitions from scratch.template.yaml — no migration to serverless.yml, no duplicate config files, no deployment step needed before you can test locally.Serverless Framework is a great deployment tool. But if local Step Functions development and debugging is your daily workflow, Thrubit will make every iteration faster.
serverless.ymlNo CLI setup. No YAML to write before your first run. No deployment step before you can test a workflow.
Download Thrubit for macOS or Windows. Double-click to install — it behaves like any other desktop application. No npm install, no CLI dependencies.
Open Preferences and point Thrubit at the folder containing your template.yaml or ASL files. It automatically discovers all Lambda functions and state machines — no config file required.
Paste your ASL JSON, drag in a template from Thrubit's workflow library, or create a new state machine from scratch using the visual designer.
Click Run. Watch the execution trace live on the visual graph. Inspect each state's input, output, timing, and errors — exactly as it flows through your workflow. No deploy required.
If your team already uses Serverless Framework and wonders how Thrubit fits in, here are the questions we hear most often.
sls deploy to push your Lambda functions and state machines to AWS. Many teams run this combination today.serverless.yml to use Thrubit?serverless.yml stays exactly as it is for deployment; Thrubit handles local development separately.serverless-step-functions plugin, which provides basic local execution but no visual debugger, no real-time execution trace, and no Bedrock mock. Thrubit was built from the ground up specifically for that workflow.Download Thrubit and run your first Step Functions workflow locally — with the real-time visual debugger that Serverless Framework doesn't have. No Docker. No AWS account. No credit card. ZERO AWS costs.
Real feedback from engineers, trainers and decision makers.
“Thrubit cut our Step Functions debugging cycle from 15 minutes per iteration down to seconds. The visual trace is worth the price alone. It’s become an essential part of our development workflow.”
“I was looking for ways to make Step Functions and Lambdas more tangible for students. Thrubit makes it significantly easier to visualize workflows and experiment locally, accelerating real understanding.”
“Thrubit saves us over $24k a year & protects us from surprise AWS bills. One rogue state machine once cost us 10x our typical month. With Thrubit, that risk is gone and our developers iterate faster.”