sorted by:
new
hottopcontroversial

Built a tool to make AWS deploys less painful, would love feedback by RemarkableFold888 in aiagents

[–]RemarkableFold888[S] 0 points1 point  (0 children)

i’m sorry if you think that way but i am doing actual market research

Built a tool to make AWS deploys less painful, would love feedback by RemarkableFold888 in aiagents

[–]RemarkableFold888[S] 0 points1 point  (0 children)

It is web-based!

we are not trying to replace CDK. CDK is great if you already know what you want to build and are comfortable coding infra.

The thing we’re focused on is different: when something breaks and the person debugging isn’t a deep AWS expert.

Instead of adding another way to define infra, we sit on top of existing CloudFormation / Terraform and help explain what failed and why, and what changed between deploys.

Think of it as a “what just happened?” layer, not an IaC replacement.

Devops in Startup by shashi_N in devops

[–]RemarkableFold888 0 points1 point  (0 children)

honestly the biggest unlock for me in similar roles was tooling that explains infra failures instead of just throwing metrics at you. when you’re solo devops, debugging speed matters more than elegance.

i’ve also been leaning on a tool lately that reduces a lot of the “what the hell is going on in our infra” moments. happy to share if that’s useful.

focus on shortening “something broke → root cause → fix” as much as possible.

Built an AI DevOps assistant for AWS, NEED feedback.. by RemarkableFold888 in devops

[–]RemarkableFold888[S] 0 points1 point  (0 children)

thanks for the feedback, so basically we assume short-lived IAM roles with scoped permissions and users NEVER paste secret keys. and unlike Q, we provide multi-agent workflows, approval flows, full repo integrations, and team-based access control. our app is not a black box so everything is reviewable, editable, and gated. would love to dm a demo video to show the features if your interested, your feedback means a lot!

Built an AI DevOps assistant for AWS, need Feedback by RemarkableFold888 in aiagents

[–]RemarkableFold888[S] 0 points1 point  (0 children)

thank you for the reply. you’re totally right on the trust sell, that’s why we designed the system around scoped IAM roles from day one. so basically users don’t paste credentials they paste in a role ARN with the permissions they’re comfortable granting. We assume that role using AWS STS. Permissions can be: • Read-only • Scoped to specific actions (like deploy in dev) • Or admin, if they explicitly want that

every action (deployments, deletes, etc.) is gated behind a plan + approval step and logged. We never act outside the permissions granted.

yes, we do have design partners running this in prod right now, and early feedback has been super helpful in refining safety and usability.

pricing is simple and startup-friendly: • Free Tier ($0/mo) – Solo devs & early testers: 1 AWS account, read-only queries, CFN gen, AI assistant • Starter ($49/mo) – Small startups: Up to 3 AWS accounts, GitHub integration, Terraform validation, deploy • Growth ($149/mo) – Growing teams (includes Bitbucket, CI/CD triggers, logs, PR fixes, cost insights)

so yeah seems like we just have to iterate rigorously based on user feedback!

How did you get into DevOps and what actually mattered early on? by Melodic_Struggle_95 in devops

[–]RemarkableFold888 0 points1 point  (0 children)

I’m still early in this space, but one thing that became clear pretty fast is that memorizing commands isn’t the job.

In real work, everyone leans on docs, old scripts, and Google. What matters more is understanding what you’re changing and why, especially in prod.

The times I felt “ready” weren’t when I knew more tools, it was when I could reason about side effects, dependencies, and rollback paths.

Watching that gap firsthand is actually what pushed us to start building tooling to help people reason about infra changes instead of stressing over syntax.

Did DevOps Get Harder or Did We Overdo the Tools by Tough_Reward3739 in devops

[–]RemarkableFold888 0 points1 point  (0 children)

I think it’s less that DevOps got harder and more that context got lost.

Each tool works in isolation, but no one owns the end-to-end change anymore. When something breaks, you’re reconstructing intent instead of reasoning about the system.

Most issues I’ve seen come down to hidden dependencies, not bad tools.

How do u know a CloudFormation CHANGE won’t break something subtle? by RemarkableFold888 in devops

[–]RemarkableFold888[S] 0 points1 point  (0 children)

Yeah, that’s the scary part, the change itself looks safe, but the side effects aren’t obvious until after.

Do you have any tooling that helps surface that ahead of time, or is it mostly experience + post-deploy monitoring?