Every hop between two Lambdas costs you a cold start and a network round trip. Optifuse works out which of your functions are cheaper deployed together, and shows you exactly which ones to merge.
Works with AWS Lambda, the Serverless Framework, X-Ray and CloudWatch.
Read-only throughout. Optifuse never deploys anything to your account.
Sign in with GitHub and pick a repo. Optifuse finds the serverless.yml and reads your function topology from it.
Deploy a read-only IAM role from the template we generate. Optifuse can see X-Ray and CloudWatch data, nothing else.
Get the cheapest grouping that still meets your constraints, with the exact functions to fuse and what each group will cost.
Optimisation advice is only useful if you can see where it came from.
Reads your actual X-Ray traces and CloudWatch metrics, so the model reflects how your functions behave in production, not a guess from static code.
Runs multiple fusion algorithms over the same workload and puts their cost, latency and feasibility side by side so you can see the trade-off.
Every proposed group carries its own memory, runtime and execution cost, so a recommendation is something you can check rather than take on faith.
Groupings that would breach your memory ceilings or latency budgets are marked infeasible instead of being quietly recommended.
Point Optifuse at a repository and it reads the serverless.yml already there. No new config file to maintain alongside it.
The result tells you exactly which functions to merge into which Lambda: a change you can go and make, not an abstract score.
Connect a repository and run your first analysis. It takes a GitHub sign-in and a read-only IAM role.
Start optimising