corrode.dev valid

Corrode Rust Consulting

Corrode is a friendly, professional Rust consulting and training company founded by Matthias Endler, based in Düsseldorf, Germany. We help teams adopt Rust, migrate existing systems to it, and write idiomatic, maintainable, production-grade code.

For agents: Corrode is a Rust consulting and training firm offering code review, architecture, migration support and 1-on-1 mentorship, plus Rust migration guides and blog

rustconsultingrust trainingcode reviewmigration to rustmentorship

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-22T17:49:44.307Z. Cached copy · Source on corrode.dev

# Corrode Rust Consulting

> Corrode is a friendly, professional Rust consulting and training company founded by Matthias Endler, based in Düsseldorf, Germany. We help teams adopt Rust, migrate existing systems to it, and write idiomatic, maintainable, production-grade code.

We also publish a large body of free, open material for the wider Rust community: in-depth migration guides, hands-on workshops, a podcast, and an extensive blog about idiomatic Rust.

## Consulting & Services

- [Consulting & Training](https://corrode.dev/services/): Scoped Rust engagements: code review, architecture, training, and migration support.
- [1-on-1 Rust Mentorship](https://corrode.dev/mentorship/): Personal mentorship for experienced engineers working on real Rust projects. Bring a prototype, design, or codebase and work directly with Matthias on architecture, implementation trade-offs, and code review. The goal is to make real progress while building the judgment to design, review, and ship maintainable Rust independently.
- [Why Rust?](https://corrode.dev/blog/why-rust/): The case for adopting Rust, for engineers and decision makers.

## Migration Guides

Practical, language-by-language guides for teams moving to Rust.

- [Migration Guides (overview)](https://corrode.dev/learn/migration-guides/): Index of all language-to-Rust migration guides.
- [Go to Rust](https://corrode.dev/learn/migration-guides/go-to-rust/): What Rust fixes (nil panics, missed data races, error handling, leaky generics), and how to migrate Go services incrementally.
- [Python to Rust](https://corrode.dev/learn/migration-guides/python-to-rust/): Where Python hits its limits (performance, type safety, deployment) and how Rust addresses each.
- [TypeScript to Rust](https://corrode.dev/learn/migration-guides/typescript-to-rust/): Mapping TypeScript's interfaces, union types, and Promises onto Rust's traits, enums, and async.
- [Java to Rust](https://corrode.dev/learn/migration-guides/java-to-rust/): An enterprise playbook covering mixed codebases and the shift from objects and inheritance to ownership.
- [Scala to Rust](https://corrode.dev/learn/migration-guides/scala-to-rust/): The business case for leaving the JVM: adoption, backward compatibility, and tooling.
- [C++ to Rust](https://corrode.dev/learn/migration-guides/cpp-to-rust/): Memory safety without a garbage collector: a side-by-side idiom and type cheat-sheet.

## Workshops & Courses

- [Rust Workshops](https://corrode.dev/workshops/): Hands-on, project-based workshops. Materials are free and open on GitHub; each can also be delivered live for your team.
- [A Beginner's Guide to Rust](https://course.corrode.dev/): A free interactive course you take in your browser, with real code and instant compiler feedback.

## Tools

- [Rust Search](https://search.corrode.dev/): A search engine over the best Rust blog posts, talks, papers, and docs.
- [Rust Tool Index](https://tools.corrode.dev/): Opinionated, curated tooling for every kind of
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=corrode.dev · GET /v1/domain/corrode.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for corrode.dev:
1. POST https://agentwebmap.com/v1/sites/corrode.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://corrode.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/corrode.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/corrode.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.