May brings a major step forward for enterprise teams: you can now sign in to Stable using your Microsoft account. We've also expanded our recommendation engine with six new checks covering Aurora, DynamoDB, OpenSearch, and EBS — helping your team find savings opportunities that are easy to miss.
Here is what's new in Stable.
1. Sign In with Microsoft (SSO)
Stable now supports Single Sign-On (SSO) via Microsoft, letting your team authenticate through your existing Microsoft / Azure Active Directory identity provider.
One click to sign in: Users on your Microsoft tenant can log in to Stable directly from the "Sign in with Microsoft" button — no Stable-specific password required.
Unified identity management: User access is controlled from the same place you manage all your Microsoft identities. Onboard a new teammate in Azure AD and they are immediately ready to access Stable.
Automatic session security: Sessions inherit your organisation's Microsoft security policies — including MFA requirements, conditional access rules, and session timeout settings — without any additional configuration in Stable.
Enterprise-ready from day one: SSO is available on all Business and Enterprise plans. Existing users can link their Stable account to their Microsoft identity from their profile settings.
To enable Microsoft SSO for your organisation, visit your workspace settings or contact our team.
2. Six New Cost Recommendations
Stable's recommendation engine now covers six additional scenarios across Aurora, DynamoDB, OpenSearch, and EBS. Each one targets a common pattern: a resource that made sense when it was provisioned but no longer matches how the workload actually runs.
Move predictable Aurora Serverless workloads to provisioned instances: Once an Aurora Serverless database shows a stable, predictable ACU range, switching to a provisioned instance — ideally covered by a Reserved Instance — can meaningfully reduce cost.
Upgrade Aurora storage from Standard to IO-Optimized: For Aurora clusters where I/O charges represent a significant share of combined storage and I/O spend, IO-Optimized storage removes per-request charges entirely and can lower the total bill.
Delete unused DynamoDB indexes: Global Secondary Indexes with no read activity over the last 30 days may be generating storage and write capacity costs for queries that are no longer happening. Stable flags them so your team can validate and clean up.
Move low-access DynamoDB tables to Standard-Infrequent Access: Tables dominated by storage costs rather than throughput can benefit from the Standard-IA table class, which offers lower storage pricing when access frequency is low.
Purchase Reserved Instances for steady OpenSearch workloads: OpenSearch nodes running consistently on On-Demand can be covered by a one- or three-year Reserved Instance for a significant reduction in hourly cost.
Delete idle EBS volumes: Volumes attached to running EC2 instances with very low I/O activity over the last 30 days are flagged for review — so your team can confirm whether the data is still needed before deciding to remove them.
For a deeper look at the logic behind each recommendation, read our full blog post.
Stay in control of your AWS spend with Stable. Contact our sales team or register today: https://app.stableapp.cloud/session/register
Optimize. Save. Innovate.