Anand Muthukrishnan

founder/ceo @localopsco to bring AIOps to your cloud.

[Anand Muthukrishnan @luckydev]

Just love the new Basecamp update. Always always at the top of keeping things super simple to work with! @basecamp @dhh @jasonfried

[Anand Muthukrishnan @luckydev]

Why is @comet @perplexity_ai asking my phone number now 😶? Why not use CloudFlare bots service to rule out api/bot traffic..

[Thariq @trq212]

https://t.co/MXt5XS4xBX

[Anand Muthukrishnan @luckydev]

@Jason I'm in

[Anand Muthukrishnan @luckydev]

claude has been shipping at maniacal speed. full on envy from our side. we are up-ing our shipping speed as we speak at localops.

[Boris Cherny @bcherny]

We doubled Claude usage on weekends, and outside 5–11am PT on weekdays for the next 2 weeks.

[Anand Muthukrishnan @luckydev]

50 Years of Thinking Different - Apple https://t.co/FFWqEBOtVA

[LocalOps Inc @localopsco]

Self-serve infrastructure is usually a mirage. It’s often just a fancy UI that still triggers a manual ticket for the DevOps team in the background.

True self-serve means a developer can provision a production-grade environment, VPC, subnets, and EKS, without ever opening the AWS console. It means they can declare a database, a cache, or an S3 bucket in a simple config file and see it appear in minutes. The stress isn't about the tools; it's about control. We want engineers to move fast, but we're terrified of the security risks that come with infrastructure freedom.

Hardened defaults and automated provisioning aren't just "nice-to-haves". They are the only way to give developers speed without sacrificing compliance. If your engineers are still waiting 48 hours for a new staging environment, you don't have a platform; you have a queue.

Is your infrastructure a launchpad or a speed bump?

Explore how your teams can achieve self-service infrastructure access using a simple JSON: https://t.co/qp17fk9ewN

#PlatformEngineering #DevOps #AWS #DeveloperExperience #InfrastructureAsCode

[LocalOps Inc @localopsco]

You didn’t move to AWS for control. You moved for the feeling of control.

Most SaaS teams transition from Heroku or other PaaS solutions like Vercel or Render, because they want to ''own the stack''. They want to escape the black box and run production on infrastructure they fully control. But there is an uncomfortable reality that hits 90 days after the migration: You didn’t just gain control. You gained a second job.

The moment you move to your own cloud account, you inherit a mountain of operational overhead. Suddenly, your application engineers, the people you hired to ship features, are wrestling with VPC subnets, IAM keys/roles, security group rules, and EC2/Kubernetes cluster configurations.

We call this ''owning our infrastructure''. In reality, the infrastructure is owning us. The tension is real: The more granular control you have over your cloud primitives, the less control you have over your actual product roadmap. If your team is spending more time managing ''plumbing'' than building products, you haven't actually scaled. You’ve just built a more expensive way to move slowly.

Are you actually in control, or are you just busy?

#AWS #DevOps #CloudInfrastructure #PlatformEngineering #B2BSaaS #EngineeringLeadership #Kubernetes #DeveloperProductivity #TechStrategy #SRE #CloudComputing

[Anand Muthukrishnan @luckydev]

@ikamalhaasan @POTUS @grok what is this?

[Anand Muthukrishnan @luckydev]

its so brutal to let us stop making localhost:3000 requests and disrupting the team, without making us pay now and with NO heads up at ALL.

[Anand Muthukrishnan @luckydev]

All of a sudden, postman stops working for the entire team and it is asking us to pay (for the ENTIRE team) to continue making requests. In the middle of shipping something critical/time-sensitive and this pay wall pop ups with no prior email warning or heads up whatsoever!! Yes, right, squeeze existing dev community to make more cash instead of growing your TAM!

[Anand Muthukrishnan @luckydev]

This is so pathetic and no one in the team recieved any email warning or heads up about this. Its a mistake of choosing a bloated platform like this from the beginning. Now we are making it a priority in the first hour of the day to move away from @getpostman to a much more dev friendly Bruno or something similar!

[LocalOps Inc @localopsco]

A common trigger for SaaS teams moving to AWS isn’t cost.
It’s enterprise customers.

As companies move upmarket, customers start asking for:
Isolated deployments

- Stronger security and compliance controls
- Private networking requirements
- Infrastructure running inside controlled environments

These requirements are difficult to support on fully managed PaaS platforms.
Enterprise customers expect infrastructure flexibility.

AWS enables SaaS teams to meet these requirements while maintaining performance, security, and scalability.
Infrastructure is no longer just about running software.
It’s about enabling enterprise growth.

#EnterpriseSoftware #AWS #CloudInfrastructure #SaaS #DevOps #PlatformEngineering

[Anand Muthukrishnan @luckydev]

@sauravstwt @csaba_kissi Stage 1-N: LocalOps + AWS 😂😂

[Anand Muthukrishnan @luckydev]

Wouldn't it be great if we can spin up auto-scaling SPOT ec2 instances in just few clicks and schedule crons and other stateless interruptible jobs there all the time. Ends up saving ~50% on compute. We're building this into LocalOps now :) #aws #devops #platformengineering

[Anand Muthukrishnan @luckydev]

If you want to migrate off to AWS, checkout our migration guide here: https://t.co/AI4fDW5C83 . We built localops to give Heroku dev experience on any cloud account. Also handling migrations from heroku (white glove). Been helping several folks move off of heroku this way. DM me if you need any help.

[Anand Muthukrishnan @luckydev]

If you want to migrate off to AWS, checkout our migration guide here: https://t.co/AI4fDW5C83 . We built localops to give Heroku dev experience on any cloud account. Also handling migrations from heroku (white glove). Been helping several folks move off of heroku this way. DM me if you need any help.

[Anand Muthukrishnan @luckydev]

If you want to migrate off to AWS, checkout our migration guide here: https://t.co/AI4fDW5C83 . We built localops to give Heroku dev experience on any cloud account. Also handling migrations from heroku (white glove). Been helping several folks move off of heroku this way. DM me if you need any help.