Skip to content
ArchGenie logo

ArchGenie

Generates cloud infrastructure code, security assessments, cost estimates and documentation from architecture descriptions across AWS, Azure and Google Cloud.

At a glanceswept 2026-09-18
Price
Price not read
Use
Emerging≈ 25 visits a month · estimate, 2026-09
Activity
Actively maintainednothing dated on the site
Company
founding year not on record
Alternatives in Developer toolsby use, among tools still maintained
  • CodeRabbitAutomatically reviews pull requests, prioritizes them by risk, and scans for security vulnerabilities.

    Established

    ≈ 24.4k visits/mo
  • GreptileReviews pull requests and tests code changes using agent swarms to catch bugs and style violations across codebases.

    Established

    ≈ 8.5k visits/mo
  • Hacktron AIAnalyzes pull requests to find exploitable vulnerabilities and generates working proofs of concept before code ships.

    Established

    ≈ 68 visits/mo
  • MunaTrustScans code for risky generated patterns, exposed secrets, and unsafe configurations in VS Code and compatible editors.

    Emerging

    71 installs/mo
  • Noah LabsAI IDE for regulated industries with airgapped operation, formal verification, and policy-aware code generation.

    Emerging

    ≈ 110 visits/mo
  • Puaro SecurityScans pull requests to detect leaked API keys, tokens, and passwords before merge using context-aware analysis.

    EmergingMaintained

    ≈ 3 visits/mo

All Developer tools tools →

Questions this page answers
  • What is ArchGenie?

    Generates cloud infrastructure code, security assessments, cost estimates and documentation from architecture descriptions across AWS, Azure and Google Cloud.

  • Do people use ArchGenie?

    Emerging: ≈ 25 visits a month · estimate, 2026-09.

  • Is ArchGenie still maintained?

    Actively maintained.

  • What are alternatives to ArchGenie?

    In Developer tools, by use: CodeRabbit, Greptile, Hacktron AI, MunaTrust, Noah Labs, Puaro Security.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.