Codreum

Products that make cloud ops & everyday workflows radically simpler. AWS tooling • AI apps • games • Web3. Build faster. Operate cleaner. See everything.

[Codreum @codreumlabs]

We went dark for ~3 months.
Here's why: we tore down our old DNS-only product and rebuilt it from the ground up.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
The old AWSPro watched one thing — your DNS. Useful, but it only ever saw one corner of your network.
The new AWSPro sees the whole map:
→ DNS & DNS Firewall
→ VPC Flow
→ NAT & endpoints
→ global posture dashboards
→ opinionated alarms, out of the box
→ AI insights that explain what changed and why, in plain language

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

The part we wouldn't compromise on:

Everything runs inside your own AWS account.

▪️ Deploy with Terraform
▪️ Your data never leaves
▪️ Even the AI (in-account Bedrock) reads your telemetry where it already lives
▪️ Our license check sees metadata, nothing more

See everything, send nothing.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
This is for the teams who can't use SaaS observability at all — regulated, security-sensitive, data-residency-bound.
You shouldn't have to choose between visibility and keeping your data home.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

AWSPro goes live July 12.

Between now and then we're building in public — the architecture calls, why DNS-only became full observability, what we learned tearing our own product apart.

We're back. 👇

#AWS #CloudComputing #DevOps #Observability #Networking #PlatformEngineering #SRE #CloudSecurity #InfraAsCode #DataResidency

[Codreum @codreumlabs]

We've talked about where your data lives.

Today, what it costs — because pricing is an architecture decision too.

Most observability pricing punishes you for growing.
Per host. Per GB ingested. A percentage of your cloud bill. The more you run, the more you pay — for watching infrastructure you're already paying AWS to run.
Your bill scales with your success. That's backwards.

We priced AWSPro flat.
→ Not per-resource
→ Not per-GB
→ Not a cut of your cloud spend
One predictable price. Scale your network as much as you want — the number doesn't move.

There's a quieter reason this matters.
Metered pricing makes you ration visibility. You start sampling, dropping logs, watching less — to keep the bill down.
The tool meant to help you see ends up teaching you to look away.

Flat pricing removes that pressure entirely.
Watch everything. Pay the same. See everything, send nothing — and know what it costs before you scale.

AWSPro goes live July 12.

#AWS #CloudComputing #DevOps #Observability #Networking #PlatformEngineering #SRE #CloudSecurity #InfraAsCode #DataResidency

[Codreum @codreumlabs]

We went dark for ~3 months.
Here's why: we tore down our old DNS-only product and rebuilt it from the ground up.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
The old AWSPro watched one thing — your DNS. Useful, but it only ever saw one corner of your network.
The new AWSPro sees the whole map:
→ DNS & DNS Firewall
→ VPC Flow
→ NAT & endpoints
→ global posture dashboards
→ opinionated alarms, out of the box
→ AI insights that explain what changed and why, in plain language

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

The part we wouldn't compromise on:

Everything runs inside your own AWS account.

▪️ Deploy with Terraform
▪️ Your data never leaves
▪️ Even the AI (in-account Bedrock) reads your telemetry where it already lives
▪️ Our license check sees metadata, nothing more

See everything, send nothing.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
This is for the teams who can't use SaaS observability at all — regulated, security-sensitive, data-residency-bound.
You shouldn't have to choose between visibility and keeping your data home.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

AWSPro goes live July 12.

Between now and then we're building in public — the architecture calls, why DNS-only became full observability, what we learned tearing our own product apart.

We're back. 👇

#AWS #CloudComputing #DevOps #Observability #Networking #PlatformEngineering #SRE #CloudSecurity #InfraAsCode #DataResidency

[Codreum @codreumlabs]

We promised to explain why “inside your own account” changed everything.

Here it is — the product decision AWSPro is built around.

Most observability tools follow the same pattern:

Your telemetry leaves your environment, lands in someone else’s cloud, and you pay to inspect your own data through their window.

For many teams, that works.

For the teams we’re building AWSPro for, it doesn’t.

Regulated teams. Security-sensitive teams. Data-residency-bound teams.

They can’t send network telemetry to a third party — not because they’re overly cautious, but because they’re not allowed to.

So the usual SaaS model doesn’t just create friction.

It locks them out.

That’s why we inverted the architecture.

AWSPro runs inside your AWS account:

→ Deployed with Terraform
→ Telemetry stays in your account
→ AI runs through in-account Amazon Bedrock
→ Your data is read where it already lives
→ Our license check sees metadata — nothing more
The shift is simple to say and hard to build:
Bring the tool to the data, not the data to the tool.

See everything. Send nothing.
AWSPro goes live July 12.

#AWS #CloudComputing #DevOps #Observability #Networking #PlatformEngineering #SRE #CloudSecurity #InfraAsCode #DataResidency

[Codreum @codreumlabs]

Yesterday, we said we tore down our old product.

Here’s the part most teams don’t like to admit:

Deleting working code is one of the hardest calls you’ll make.

The old AWSPro did one thing well — DNS observability.

It worked. Customers paid for it.

And we retired it.

Not because it was broken, but because it was too narrow.

It watched one corner of the network and called it observability.

The easy path would have been to keep bolting features onto the foundation we already had.

But patches on a narrow base always show their seams.

So we made the expensive choice:

Rebuild the foundation, not just the feature list.

That reset changed everything.

AWSPro is no longer just DNS monitoring. It’s being rebuilt as broader AWS observability — designed to run in-account, closer to the signals, with cleaner workflows for operators.

The lesson we keep relearning:

The hardest thing to delete is the thing that’s working “well enough.”

And “well enough” is how good products quietly stop becoming great.

More on what we rebuilt — and why in-account changed everything — this week.

AWSPro goes live July 12.

#AWS #CloudComputing #DevOps #Observability #Networking #PlatformEngineering #SRE #CloudSecurity #InfraAsCode #DataResidency

[Codreum @codreumlabs]

Update: we renamed our OSS repo from terraform-aws-dns-monitoring-nxdomain → terraform-aws-observability-core.

Why: it’s no longer just NXDOMAIN. This repo now includes:

✅ NXDOMAIN module

✅ lightweight VPC provisioning module
…and we’ll keep adding/improving modules over time.

New home: https://t.co/ekxQSHuqG1

#AWS #Terraform #CloudWatch #SRE #DevOps

[Codreum @codreumlabs]

Small milestone: Codreum was accepted into AWS Activate (Founder).

It helps us move faster on Codreum Labs — especially DNS Monitoring Pro (Terraform → CloudWatch) + more production testing.

OSS NXDOMAIN: https://t.co/GtANfIcog6

Pro docs: https://t.co/WZr6XlhbmH

#AWS #Startups #SRE #DevOps

[Codreum @codreumlabs]

Our primary target audience is startups, SMEs, and software companies that need scalable cloud-based solutions for finance automation, infrastructure monitoring, software licensing, and marketing automation. We also serve developers and DevOps teams looking for AWS-based infrastructure tools, while our gaming products target casual and mid-core mobile players.

[Codreum @codreumlabs]

https://t.co/2Pu24mG7bw

Codreum is building a portfolio of AWS-based SaaS products, infrastructure tools, and mobile games under Codreum Apps, Codreum Labs, and Codreum Play. Our products include accounting and finance automation tools, DNS monitoring and cloud infrastructure solutions, startup marketing automation SaaS, and License-as-a-Service platforms that let software companies issue, validate, manage, and enforce custom product licenses through a SaaS console and APIs. We also build cartoon-style 2D PvE/PvP games. We use AWS to create scalable, secure, multi-tenant products across web, cloud, and mobile.

[Codreum @codreumlabs]

https://t.co/2Pu24mG7bw

Codreum is building a portfolio of AWS-based SaaS products, infrastructure tools, and mobile games under Codreum Apps, Codreum Labs, and Codreum Play. Our products include accounting and finance automation tools, DNS monitoring and cloud infrastructure solutions, startup marketing automation SaaS, and License-as-a-Service platforms that let software companies issue, validate, manage, and enforce custom product licenses through a SaaS console and APIs. We also build cartoon-style 2D PvE/PvP games. We use AWS to create scalable, secure, multi-tenant products across web, cloud, and mobile.

[Codreum @codreumlabs]

Update from Codreum Labs: DNS Monitoring Pro is almost ready.

Built for teams that need deeper DNS visibility + faster incident workflows (Terraform → CloudWatch).

Docs/live repo: https://t.co/WZr6XlhbmH

Start now (OSS NXDOMAIN): https://t.co/GtANfIcog6
#AWS #Terraform #CloudWatch #SRE #DevOps

[Codreum @codreumlabs]

Update from Codreum Labs: DNS Monitoring Pro is almost ready.

Built for teams that need deeper DNS visibility + faster incident workflows (Terraform → CloudWatch).

Docs/live repo: https://t.co/WZr6XlhbmH

Start now (OSS NXDOMAIN): https://t.co/GtANfIcog6
#AWS #Terraform #CloudWatch #SRE #DevOps

[Codreum @codreumlabs]

NXDOMAIN spikes are often the first “DNS is breaking” signal… but most teams don’t see it until users complain.

We shipped OSS NXDOMAIN monitoring → CloudWatch, deployed via Terraform:

https://t.co/GtANfIcog6

What would you alert on: raw NXDOMAIN rate, spike vs baseline, or per-VPC/service?

#AWS #Terraform #CloudWatch #SRE #DevOps

[Codreum @codreumlabs]

NXDOMAIN spikes are often the first “DNS is breaking” signal… but most teams don’t see it until users complain.

We shipped OSS NXDOMAIN monitoring → CloudWatch, deployed via Terraform:

https://t.co/GtANfIcog6

What would you alert on: raw NXDOMAIN rate, spike vs baseline, or per-VPC/service?

#AWS #Terraform #CloudWatch #SRE #DevOps

[Codreum @codreumlabs]

AWS + OpenAI expanding their partnership is a big signal: production-scale agents are becoming real infrastructure.

At Codreum Labs we’re focused on the “boring but critical” layer: operability — clear signals, fast incident workflows, fewer mysteries.

If you’re running agents in AWS, what’s the hardest part today: state, observability, or cost control?

#AWS #Bedrock #GenAI #SRE #DevOps

[Codreum @codreumlabs]

Totally agree — state drift → observability gaps → cost surprises is the nasty compounding loop.
Treating agent state as an audit surface from day one feels like the right default.
Curious: what are the minimum “must-log” fields you’d require (state transitions, tool calls, retries, token/cost per step, actor/tenant)?

[Codreum @codreumlabs]

AWS + OpenAI expanding their partnership is a big signal: production-scale agents are becoming real infrastructure.

At Codreum Labs we’re focused on the “boring but critical” layer: operability — clear signals, fast incident workflows, fewer mysteries.

If you’re running agents in AWS, what’s the hardest part today: state, observability, or cost control?

#AWS #Bedrock #GenAI #SRE #DevOps