Cloud 66
@cloud66

Deploy your code directly from your repo to any cloud in minutes. Have a question? Book a demo at cloud66.com #RubyonRails #Kubernetes #JAMstack #DevOps

 London, San Francisco
cloud66.com
Joined July 2011
5,186 Photos and videos
From "Hello World" to KeepAlive with Cloud 66. cloud66.com/
From Hello World to KeepAlive with Cloud 66

ALT From Hello World to KeepAlive with Cloud 66
2
6
1,100
Cloud 66 retweeted
Kash Sajadi
@khash
Aug 28
The new DMARC feature from @getsendops is really good! With MCP support you can leave domain authentication to your agent.
2
2
116
AI assistants have made shipping code effortless. But they lack context about your actual production environment. Unoptimized queries and silent failures are the hidden tax of AI-generated code. Day 2 operations is where the real work begins.
1
2
314
Traditional monitoring just tells you if a server is up. With LLM-written code, you need deep, infrastructure-level visibility. You must know exactly which automated script is locking your database before it causes a major outage.
1
66
We are diving deep into how to bridge this governance gap and maintain control over AI-generated software. Read our guide on Day 2 operations and observability: blog.cloud66.com/observabili…

Observability for AI-Generated Code: Bridging the New Governance Gap

We are witnessing the fastest expansion of the software development lifecycle in history. Generative AI tools have turned every developer into a hyper-productive builder, and in some cases, turned...

blog.cloud66.com
1
44
AI lets us write and deploy code in seconds. But it is creating a massive, silent risk: instant vendor lock-in. When an AI assistant builds an app, it defaults to the easiest path, usually proprietary PaaS ecosystems. And nobody realizes until the bill arrives.
2
1
333
more replies
Once in production, lock-in costs you: - Migration pain rewriting config files - Pricing exposure with zero leverage when subscription fees spike - Platform risk if your vendor degrades - Data risk with customer data sitting on shared, multi-tenant hardware.
1
28
To scale safely, you must own your infrastructure: run in your own cloud, isolate your data, and avoid proprietary runtimes. Read the full breakdown on the blog: blog.cloud66.com/the-governa…

The Governance Blind Spot: Vendor Lock-In in the AI Development Era

AI tools ship code faster than teams can evaluate platform choices. This makes vendor lock-in a key governance risk. Here is how to regain infrastructure ownership.

blog.cloud66.com
18
AI can write a fully functional microservice in 15 seconds. But code is not an application, and shipping is not operating. When anyone can generate thousands of lines of code with a simple prompt, the bottleneck shifts to Day 2 operations.
1
327
An AI model does not wake up at 2 AM when a memory leak starves your cluster. Without guardrails, unlimited code generation just means fragmented infrastructure, random databases, and massive cloud bills that nobody understands.
1
73
The platform team's job is shifting from manual provisioning to setting up guardrails. You need PaaS simplicity but on your own cloud. We broke down exactly how to build this framework on our blog: blog.cloud66.com/what-the-pl…

What the Platform Team Actually Does When Everyone is an AI-Assisted Builder

AI has made it easier than ever to build software. But someone still needs to make sure all that new code is secure, reliable, and actually works in production. This post looks at how the platform...

blog.cloud66.com
49
Cloud 66 retweeted
Kash Sajadi
@khash
Aug 3
We finally cancelled our Klaviyo subscription and moved to SendOps (sendops.dev). Liberating!

Email Operations Platform on Your Amazon SES | SendOps

Run transactional, lifecycle, and marketing email from your own AWS SES account — audiences, broadcasts, workflows, templates, analytics, and alerts.

sendops.dev
2
1
98
Okay let's be real: when "everyone owns deployment" it really just means "nobody owns deployment." AI created more builders, but not more deployment owners. Now, it's time to assign accountability. Here are a few thoughts: blog.cloud66.com/who-owns-de…

Who Owns Deployment Governance? Structuring Accountability in the AI Era

When AI lets "anyone" write and ship code, deployment ownership defaults to "everyone." Which means nobody owns it until something breaks...at 2 AM. Check out our post for a few key ideas on how to...

blog.cloud66.com
1
1
280
When AI lets everyone in your company deploy apps, security can break fast. A stale credential plus an unpatched container is not two minor issues. It is a compounding, systemic disaster.
1
195
We built a 10-point checklist to help you evaluate your current setup across infrastructure and access controls. Check it out here: blog.cloud66.com/security-at…

Security at Scale: What Changes When Everyone Can Deploy using AI

In our first series post, The New Software Creator, we mapped out a structural shift in the industry where more users are able to use AI to 'develop,' and while that's not necessarily a problem, the...

blog.cloud66.com
37
AI's real gift to small dev teams isn't speed. It's thoroughness. It's finally writing those tedious edge-case tests, doing rigorous code reviews, and handling painful migrations that used to get deferred. The floor of what a tiny team can ship just went way up. The smaller you are, the bigger the leverage. A solo founder can now run a full, enterprise-grade development lifecycle because the cost of doing things right just plummeted. Read more on how AI levels the playing field: blog.cloud66.com/the-leverag…

The Leverage of using AI is Bigger the Smaller You Are

Last month our test count looked like it belonged to a different team, and nobody had announced a thing. The common story about AI is that it makes you faster. The more interesting one is that it...

blog.cloud66.com
2
2
94
AI means anyone can build software now. Great for velocity, terrifying for security. Since DevOps headcount isn't scaling to match, you can't police the code. But you can govern the deployment. Good governance isn't bureaucracy; it's making the safe path the easiest. 3 questions: 1. Can anyone bypass CI/CD? 2. Are production change trails automated? 3. Is the secure path the fastest? If not, you have a governance gap. Read more: blog.cloud66.com/when-anyone…

When Anyone Can Build Software, Deployment Governance Is What Keeps It Safe

As AI makes it possible for almost anyone to build software, the challenge is no longer writing code. It's deploying it safely. This post explores why deployment governance has become the critical...

blog.cloud66.com
1
2
100
Everyone's talking about AI making developers faster. The bigger shift? AI is creating millions of new software creators. The bottleneck isn't writing code anymore. It's deploying it safely. Governance just became a lot more important. blog.cloud66.com/the-new-sof… #AI #DevOps #PlatformEngineering

The New Software Creator: Why AI Changes the Governance Problem, Not Just the Speed Problem

The bottleneck in software delivery is no longer writing the code. AI has expanded who builds software — and every new app is a new operational obligation. Here's why deployment governance is the...

blog.cloud66.com
2
418
Cloud 66 retweeted
SendOps
@getsendops
May 13
High bounce rates and elevated complain rates can result in banning your AWS SES account immediately. This can really hurt your operations. Here is a detailed guide on preventing those and what to do in case the block happnes:
1
2
206
we almost made auto-scaling a premium feature. the thinking was: small teams don't need it. they can just resize manually when traffic spikes. that was wrong. small teams are exactly the ones who can't afford to be paged at 2am because a campaign went live and their app fell over. they don't have an on-call rotation. they don't have someone watching dashboards. they just have engineers who need to sleep. so we shipped auto-scaling for everyone. based on real signals; CPU, memory, queue backlog, Nginx response time. not a fixed schedule. not a guess. actual behavior from your app. the teams who use it most aren't the big ones. they're the 4-person teams who got burned once and never want to think about it again.
2
127
Load more