Simantic growth playbook

Build a public /mcus page from the same data `sim models` already ships: each chip's status (modeled, in progress, not modeled), the peripherals and buses modeled, the supported build systems and the sim version it arrived in. Give each released chip its own page (for example /mcus/stm32f401re) with a ten-line runnable example, the PR-review setup for that chip and its validation status. Add a "request a chip" button that asks for the part number and the use case. Link the list from the homepage hero ("Runs today on STM32F0/F4/H7, ESP32 and RP2040"), the Cloud Sim page, pricing and the PR-review docs, and date each new model so the weekly additions show as visible progress.

It answers the qualifying question before signup, prevents wasted static reviews, and gives Simantic pages that match how engineers search ("STM32F401RE simulator", "simulate ESP32-C3 firmware"). Chip requests become a demand-ranked modeling roadmap. Renode leads with its public board list for the same reason.

[ ] /mcus table generated from `sim models --show-unmodeled`
[ ] Status per chip: modeled / in progress / not modeled
[ ] Buses and peripherals modeled per chip
[ ] Build systems: CubeMX make, make, CMake, pico-sdk, ESP-IDF, Zephyr
[ ] One page per released chip with a runnable example
[ ] "Request a chip" form (part number, use case)
[ ] Hero line on the homepage linking to /mcus
[ ] Links from /cloud-sim, /pricing and /docs/pr-review
[ ] Static-review message links to /mcus
[ ] Release date on each newly modeled chip
[ ] Pages added to the sitemap

• The public list drifts from what the binary supports

  Generate it from the same source as `sim models` on every release.

• A short list looks thin against Renode's 1200+ boards

  Lead with depth per chip (buses, timing, validation) and show requests and release dates.

• Your websiteHomepage: H1 "Real firmware. Simulated hardware."; Cloud Sim access is listed as HTTP API, TypeScript and MCP, with "Python" and "CLI" marked "Coming soon"; the AI firmware review section shows a sample review of an STM32F072RB blinky project; the hero visual shows I2C and RC rise-time waveforms; "Backed by Y Combinator"; no customers, logos or testimonials, and no list of supported microcontrollers.Source
• Your websiteCloud Sim page (/cloud-sim), the target of the homepage "Try Cloud Sim" button, checked twice on November 9, 2026: its whole body is "Introducing Cloud Sim" and "Cloud Sim lets you run your firmware from anywhere, with minimal setup." It names no chip and has no code sample or steps; the only next step is the Dashboard link.Source
• Your websiteDocs (/docs): the `sim` CLI installs with one curl command on macOS (Apple Silicon) or Linux x64, and on Windows only through WSL2; it needs Python 3.12+ with its shared library, and every run needs a Simantic account. The sample `sim models` output lists RP2040, STM32F072RB, STM32F401RE and "..."; the STM32H743 and STM32H753 parts are "modeled since sim 0.8" while other H7 parts are "not-modeled". "Usage reporting is required in this build and has no opt-out": each command reports its options, duration, OS and, for runs, the ELF size and SHA-256 (firmware and UART output are not sent).Source
• Your websiteGuide (/docs/guide): examples name STM32F401RE, STM32H753IITX, STM32G474RE, STM32F767ZI, NRF52840QIAA and ESP32-C3, C6 and S3, and point to `sim models` for the list; modeled buses include UART, I2C, SPI, CAN FD, BLE, 802.15.4, Ethernet, Wi-Fi, SD/MMC, USB, GPIO, timers and DMA; Python "peers" stand in for sensors and other parts; "`--timeout` is virtual seconds".Source
• Your websitePR reviewer docs (/docs/pr-review): mention @simantic-bot in a pull request and it builds the firmware, runs scenarios designed from the diff in the simulator and posts one review; it is "an on-demand assistant, not CI: nothing runs on a push"; "a pull request for any other MCU gets a static review, without simulation and never approved"; reviews draw on "$10 a month on the Community plan, $200 on Developer", shared with simulation runs, and are refused with less than $1.50 left; enterprise groups are billed as a group; reviews are private by default and can be shared by link; the diff, build output and simulator output are sent to the company's model provider.Source
• News coverageAI Weekly (October 30, 2026): the engine was written from scratch in Rust rather than wrapping Renode or QEMU, citing development speed, performance and timing accuracy; the platform offers virtual dev boards by API, simulation-checked AI code review and CI that validates every commit; launch chips are STM32F0/F4/H7, ESP32-S3/C3 and RP2040, with new models arriving weekly; the company cites hardware validation rigs running around the clock; target uses include flight controllers, EVs, robotics and satellites.Source
• Competitor researchRenode (Antmicro's platform page): an open-source emulation framework claiming 1200+ supported boards, 12+ CPU architectures and 800+ peripheral models, with public Zephyr and U-Boot test dashboards per board, integrations with GitHub Actions, GitLab and Jenkins, and paid services for peripheral modeling and CI setup.See the research Source

Rebuild /cloud-sim as a quickstart: the install line, a run command against a sample ELF, the actual UART output and a pass/fail `--expect` line, then tabs for CLI, HTTP API, TypeScript and MCP showing the same run. Add the chip list (idea 1), what a run costs in credits (idea 3) and one signup button.

Developer tools convert when visitors can see the exact command and its output before signing up. The page already gets the homepage's main click.

• Commands change between releases

  Pull snippets from the docs source so they update together.

• Your websiteCloud Sim page (/cloud-sim), the target of the homepage "Try Cloud Sim" button, checked twice on November 9, 2026: its whole body is "Introducing Cloud Sim" and "Cloud Sim lets you run your firmware from anywhere, with minimal setup." It names no chip and has no code sample or steps; the only next step is the Dashboard link.Source
• Your websiteDocs (/docs): the `sim` CLI installs with one curl command on macOS (Apple Silicon) or Linux x64, and on Windows only through WSL2; it needs Python 3.12+ with its shared library, and every run needs a Simantic account. The sample `sim models` output lists RP2040, STM32F072RB, STM32F401RE and "..."; the STM32H743 and STM32H753 parts are "modeled since sim 0.8" while other H7 parts are "not-modeled". "Usage reporting is required in this build and has no opt-out": each command reports its options, duration, OS and, for runs, the ELF size and SHA-256 (firmware and UART output are not sent).Source
• npmTwo packages: @simantic/cloud-sim (35 weekly downloads) and @simantic/cloud-sim-mcp (29 weekly downloads), the TypeScript SDK and MCP server linked from the homepage.Source

Under each plan, add typical usage: about N simulated minutes or M PR reviews a month, based on real median costs. Mark Community "Free". Add an FAQ: what a credit is, what a typical review and run cost, what happens when credits run out, how the overage budget works, and the difference between monthly and annual billing.

Usage pricing in dollars without units makes engineers guess and stall. Concrete equivalents let them choose a plan, and they make the $1,000 annual Developer plan easier to justify to a manager.

• Costs vary widely by firmware

  Show a typical range and the p90.

• Printing unit costs fixes expectations

  Call them estimates and date them.

• Your websitePricing page: Community ("For individuals getting started", no price shown, "$10 in monthly credits", 3 concurrent simulation runs, GitHub integration, "Sign up"); Developer ("For professional engineers", $100 a month or $1,000 a year, shown as $83.33/mo, "$200 in monthly credits", 10 concurrent runs, early access to simulation models); Enterprise ("Contact Us": unlimited API usage, unlimited concurrent runs and PR reviews, private hosting, custom subdomain and SSO, custom SLA). There is no FAQ and no explanation of what a credit buys.Source
• Your websitePR reviewer docs (/docs/pr-review): mention @simantic-bot in a pull request and it builds the firmware, runs scenarios designed from the diff in the simulator and posts one review; it is "an on-demand assistant, not CI: nothing runs on a push"; "a pull request for any other MCU gets a static review, without simulation and never approved"; reviews draw on "$10 a month on the Community plan, $200 on Developer", shared with simulation runs, and are refused with less than $1.50 left; enterprise groups are billed as a group; reviews are private by default and can be shared by link; the diff, build output and simulator output are sent to the company's model provider.Source
• Competitor researchWokwi (homepage and pricing): "World's most advanced ESP32 simulator", running in the browser for Arduino, ESP32, STM32 and Raspberry Pi Pico; Community is €0 with unlimited simulations; Wokwi Pro is €20 per seat a month with "2000 monthly CI minutes", VS Code and JetBrains plug-ins and team billing.See the research Source

Change "CLI (coming soon)" to "CLI" linked to the docs install, and "Python (coming soon)" to "Python (alpha)" linked to the pippy README, with a four-line pytest example. Check every other "coming soon" or stale claim on the site at each release.

The CLI and Python are the interfaces embedded test engineers reach for first. Showing them costs nothing and removes a reason to leave.

• Alpha users hit breaking changes

  Label it alpha and pin versions, as the README already advises.

• Your websiteHomepage: H1 "Real firmware. Simulated hardware."; Cloud Sim access is listed as HTTP API, TypeScript and MCP, with "Python" and "CLI" marked "Coming soon"; the AI firmware review section shows a sample review of an STM32F072RB blinky project; the hero visual shows I2C and RC rise-time waveforms; "Backed by Y Combinator"; no customers, logos or testimonials, and no list of supported microcontrollers.Source
• Your websiteDocs (/docs): the `sim` CLI installs with one curl command on macOS (Apple Silicon) or Linux x64, and on Windows only through WSL2; it needs Python 3.12+ with its shared library, and every run needs a Simantic account. The sample `sim models` output lists RP2040, STM32F072RB, STM32F401RE and "..."; the STM32H743 and STM32H753 parts are "modeled since sim 0.8" while other H7 parts are "not-modeled". "Usage reporting is required in this build and has no opt-out": each command reports its options, duration, OS and, for runs, the ELF size and SHA-256 (firmware and UART output are not sent).Source
• GitHubThe simantic-dev organization has 17 public repositories, all at 0 stars: `pippy` ("Test firmware without a board: Python SDK and pytest plugin", alpha 0.4.x, "not distributed on PyPI"); `embedded-ci-action` (a GitHub Action that submits firmware .elf files for simulation, with results in the dashboard's Embedded CI tab; no releases, used at @main); `examples` (good and faulty scripted peers per bus: GPS and RC links over UART, a barometer, power monitor and accelerometer over I2C, an IMU over SPI, DroneCAN and Ethernet; "No firmware is included"); and forks of Zephyr, QEMU and open-source flight-controller, e-reader, solar-car and student racing firmware.Source

Tag v1 of the action and its setup step, publish it to the GitHub Marketplace, and add a /ci page: the workflow YAML, what a CI run costs in credits, what fails a build (`--expect` and `--expect-absent`), and a screenshot of the Embedded CI tab. Link /ci from the homepage and pricing, and from the PR reviewer docs ("for every push, use CI").

CI is a recurring use that consumes credits every day, which is what turns a $10 trial into a Developer or Team plan. The Marketplace is where firmware teams look for actions.

• CI runs exhaust Community credits quickly

  Show per-run cost and a warning before the allowance runs out.

• GitHubThe simantic-dev organization has 17 public repositories, all at 0 stars: `pippy` ("Test firmware without a board: Python SDK and pytest plugin", alpha 0.4.x, "not distributed on PyPI"); `embedded-ci-action` (a GitHub Action that submits firmware .elf files for simulation, with results in the dashboard's Embedded CI tab; no releases, used at @main); `examples` (good and faulty scripted peers per bus: GPS and RC links over UART, a barometer, power monitor and accelerometer over I2C, an IMU over SPI, DroneCAN and Ethernet; "No firmware is included"); and forks of Zephyr, QEMU and open-source flight-controller, e-reader, solar-car and student racing firmware.Source
• Your websitePR reviewer docs (/docs/pr-review): mention @simantic-bot in a pull request and it builds the firmware, runs scenarios designed from the diff in the simulator and posts one review; it is "an on-demand assistant, not CI: nothing runs on a push"; "a pull request for any other MCU gets a static review, without simulation and never approved"; reviews draw on "$10 a month on the Community plan, $200 on Developer", shared with simulation runs, and are refused with less than $1.50 left; enterprise groups are billed as a group; reviews are private by default and can be shared by link; the diff, build output and simulator output are sent to the company's model provider.Source
• Your websiteSitemap (14 URLs, checked November 9, 2026): the homepage, /cloud-sim, /pricing, /validation, /contact, /investors, /apply, /blog, /privacy, /terms and four docs pages (/docs, /docs/guide, /docs/pr-review, /docs/simantic-json). There are no supported-chip, CI, use-case, changelog or comparison pages, and the blog says only "We're working on it. Check back later."Source
• News coverageAI Weekly (October 30, 2026): the engine was written from scratch in Rust rather than wrapping Renode or QEMU, citing development speed, performance and timing accuracy; the platform offers virtual dev boards by API, simulation-checked AI code review and CI that validates every commit; launch chips are STM32F0/F4/H7, ESP32-S3/C3 and RP2040, with new models arriving weekly; the company cites hardware validation rigs running around the clock; target uses include flight controllers, EVs, robotics and satellites.Source
• Competitor researchWokwi (homepage and pricing): "World's most advanced ESP32 simulator", running in the browser for Arduino, ESP32, STM32 and Raspberry Pi Pico; Community is €0 with unlimited simulations; Wokwi Pro is €20 per seat a month with "2000 monthly CI minutes", VS Code and JetBrains plug-ins and team billing.See the research Source

Render each open role into the /apply page as static HTML with the full description, add JobPosting structured data, redirect /careers to /apply, and link the Y Combinator listing. Add a short "why join" section: the from-scratch Rust engine, the hardware validation rigs and the backers.

Senior simulation researchers are rare and research a company before applying. A page that search engines and job aggregators can read widens the funnel for the most important hire.

• Roles go stale on the page

  Generate the page from the same source as the job board.

• Your websiteCareers page (/apply, the footer's "Careers" link), read November 9, 2026: a reader that does not run scripts sees only "Join us", "Open roles at Simantic" and "Loading…"; no role title or description is in the page. /careers returns a 404.Source
• HiringLead Simulation Researcher (Electronics / Firmware), Waterloo or San Francisco, $200K-$300K and 2.00%-5.00% equity, 6+ years: to "lead Simantic's efforts to develop an electronics simulation platform based on SPICE and Xyce for agentic AI use", prototyping hardware to check that the simulation physics matches real-world behavior. The listing describes a team of 4.Source

Add three short fields: target MCU (a dropdown from the chip list, plus "other"), industry, and CI system. Show a calendar link on the thank-you page. Route "other" chips to the modeling backlog and send an instant reply with the matching chip page or the nearest supported part.

Qualifying before the call shortens the cycle, and a booking link captures intent while the visitor is still on the page.

• More fields lower submissions

  Keep them optional dropdowns.

• #1 Publish one public list of supported microcontrollers, and link it from the homepage, Cloud Sim and pricing

• Your websiteContact page ("Modernize your team's firmware workflows"): a form for first and last name, job title, company, work email and "How can we help?"; no booking link, no email address and no question about the target chip, industry or CI system.Source
• Y CombinatorLaunch post: "We built the world's first agent-first firmware simulator"; Cloud Sim is "the first virtual devboard you can program and run entirely from your terminal" and needs only an MCU model and a compiled ELF; Pyrite can run locally in CI/CD or agent harnesses for select partners; the founders, formerly in firmware and hardware roles at Tesla, Neuralink, NXP and Onsemi, ask to hear from teams in automotive, robotics or aerospace. No traction or customers are disclosed.Source
• Your websitePricing page: Community ("For individuals getting started", no price shown, "$10 in monthly credits", 3 concurrent simulation runs, GitHub integration, "Sign up"); Developer ("For professional engineers", $100 a month or $1,000 a year, shown as $83.33/mo, "$200 in monthly credits", 10 concurrent runs, early access to simulation models); Enterprise ("Contact Us": unlimited API usage, unlimited concurrent runs and PR reviews, private hosting, custom subdomain and SSO, custom SLA). There is no FAQ and no explanation of what a credit buys.Source

For each released chip, publish a dated validation report: the test suite (instructions, peripherals, timing, multi-device scenarios), the pass rate against real silicon, the known simplifications and any open mismatches, tied to the sim version. Put a status badge on each chip page from idea 1 and offer a downloadable report for enterprise security and quality reviews.

Accuracy is the deciding question for simulation. Publishing it, including the gaps, turns the validation principle into proof that competitors don't show per chip.

• Published gaps are used against Simantic

  Pair each gap with its fix date; the honesty is the differentiator.

• #1 Publish one public list of supported microcontrollers, and link it from the homepage, Cloud Sim and pricing

• Your websiteValidation page: principles such as "Let real hardware be the reference", "Look beyond a successful boot", "Make failures part of the test" and "Show the evidence. Name the boundaries.", and "We are building toward a validation standard that firmware simulation has not seen before." It names no chips and shows no numbers or results; the call to action is "Talk to the team".Source
• News coverageAI Weekly (October 30, 2026): the engine was written from scratch in Rust rather than wrapping Renode or QEMU, citing development speed, performance and timing accuracy; the platform offers virtual dev boards by API, simulation-checked AI code review and CI that validates every commit; launch chips are STM32F0/F4/H7, ESP32-S3/C3 and RP2040, with new models arriving weekly; the company cites hardware validation rigs running around the clock; target uses include flight controllers, EVs, robotics and satellites.Source
• Y CombinatorLaunch post: "We built the world's first agent-first firmware simulator"; Cloud Sim is "the first virtual devboard you can program and run entirely from your terminal" and needs only an MCU model and a compiled ELF; Pyrite can run locally in CI/CD or agent harnesses for select partners; the founders, formerly in firmware and hardware roles at Tesla, Neuralink, NXP and Onsemi, ask to hear from teams in automotive, robotics or aerospace. No traction or customers are disclosed.Source
• Competitor researchRenode (Antmicro's platform page): an open-source emulation framework claiming 1200+ supported boards, 12+ CPU architectures and 800+ peripheral models, with public Zephyr and U-Boot test dashboards per board, integrations with GitHub Actions, GitLab and Jenkins, and paid services for peripheral modeling and CI setup.See the research Source

Publish a short weekly post or /changelog entry: new chips and peripherals modeled, validation changes, CLI and SDK releases, and one example run. Offer an RSS feed and an email digest, and repost each entry to LinkedIn. Once a month, write one deeper engineering post (how a peripheral was modeled, or a timing bug found against silicon).

Weekly releases show a young company is moving, give returning visitors a reason to come back, and build search pages for each newly supported part.

• Cadence slips

  Generate a draft from release notes automatically.

• Your websiteSitemap (14 URLs, checked November 9, 2026): the homepage, /cloud-sim, /pricing, /validation, /contact, /investors, /apply, /blog, /privacy, /terms and four docs pages (/docs, /docs/guide, /docs/pr-review, /docs/simantic-json). There are no supported-chip, CI, use-case, changelog or comparison pages, and the blog says only "We're working on it. Check back later."Source
• News coverageAI Weekly (October 30, 2026): the engine was written from scratch in Rust rather than wrapping Renode or QEMU, citing development speed, performance and timing accuracy; the platform offers virtual dev boards by API, simulation-checked AI code review and CI that validates every commit; launch chips are STM32F0/F4/H7, ESP32-S3/C3 and RP2040, with new models arriving weekly; the company cites hardware validation rigs running around the clock; target uses include flight controllers, EVs, robotics and satellites.Source
• Your websiteDocs (/docs): the `sim` CLI installs with one curl command on macOS (Apple Silicon) or Linux x64, and on Windows only through WSL2; it needs Python 3.12+ with its shared library, and every run needs a Simantic account. The sample `sim models` output lists RP2040, STM32F072RB, STM32F401RE and "..."; the STM32H743 and STM32H753 parts are "modeled since sim 0.8" while other H7 parts are "not-modeled". "Usage reporting is required in this build and has no opt-out": each command reports its options, duration, OS and, for runs, the ELF size and SHA-256 (firmware and UART output are not sent).Source

Run Simantic Bot on recent pull requests in public firmware projects that target supported chips. When it finds a genuine issue, confirm it, report it upstream through the project's normal process, and, with the maintainers' agreement, publish a "found in the wild" page: the bug, the simulator evidence and the fix. Offer free reviews to the maintainers of those projects.

It shows the product working on code people know, earns goodwill and links from open-source communities, and produces a steady stream of technical stories for the changelog and social posts.

• False positives annoy maintainers

  Only report findings that are reproduced by hand.

• Projects object to publicity

  Publish only with consent; otherwise keep it private.

• GitHubThe simantic-dev organization has 17 public repositories, all at 0 stars: `pippy` ("Test firmware without a board: Python SDK and pytest plugin", alpha 0.4.x, "not distributed on PyPI"); `embedded-ci-action` (a GitHub Action that submits firmware .elf files for simulation, with results in the dashboard's Embedded CI tab; no releases, used at @main); `examples` (good and faulty scripted peers per bus: GPS and RC links over UART, a barometer, power monitor and accelerometer over I2C, an IMU over SPI, DroneCAN and Ethernet; "No firmware is included"); and forks of Zephyr, QEMU and open-source flight-controller, e-reader, solar-car and student racing firmware.Source
• Your websitePR reviewer docs (/docs/pr-review): mention @simantic-bot in a pull request and it builds the firmware, runs scenarios designed from the diff in the simulator and posts one review; it is "an on-demand assistant, not CI: nothing runs on a push"; "a pull request for any other MCU gets a static review, without simulation and never approved"; reviews draw on "$10 a month on the Community plan, $200 on Developer", shared with simulation runs, and are refused with less than $1.50 left; enterprise groups are billed as a group; reviews are private by default and can be shared by link; the diff, build output and simulator output are sent to the company's model provider.Source
• Your websiteHomepage: H1 "Real firmware. Simulated hardware."; Cloud Sim access is listed as HTTP API, TypeScript and MCP, with "Python" and "CLI" marked "Coming soon"; the AI firmware review section shows a sample review of an STM32F072RB blinky project; the hero visual shows I2C and RC rise-time waveforms; "Backed by Y Combinator"; no customers, logos or testimonials, and no list of supported microcontrollers.Source

Offer competition teams boosted Community credits, a shared org install of Simantic Bot and CI, and a channel for support, in exchange for a short case study and feedback on missing peripherals. Start with Waterloo design teams, then student engineering competitions across North America.

It builds a cohort of engineers who learn on Simantic and carry it into industry, while producing real-world case studies and modeling requests from demanding firmware.

• Teams use chips not yet modeled

  Pick teams on supported chips first; log the rest as requests.

• #5 Give the GitHub Action a release, a Marketplace listing and a CI page on the site

• GitHubThe simantic-dev organization has 17 public repositories, all at 0 stars: `pippy` ("Test firmware without a board: Python SDK and pytest plugin", alpha 0.4.x, "not distributed on PyPI"); `embedded-ci-action` (a GitHub Action that submits firmware .elf files for simulation, with results in the dashboard's Embedded CI tab; no releases, used at @main); `examples` (good and faulty scripted peers per bus: GPS and RC links over UART, a barometer, power monitor and accelerometer over I2C, an IMU over SPI, DroneCAN and Ethernet; "No firmware is included"); and forks of Zephyr, QEMU and open-source flight-controller, e-reader, solar-car and student racing firmware.Source
• News coverageUniversity of Waterloo news (July 31, 2026): the founders met the problem in co-op roles where engineers often waited weeks or months for physical devices; the company started in September 2025 and was accepted into Velocity's startup program and Y Combinator's Fall 2026 batch; it has raised about $600,000 USD; the founders met customers, design partners and investors in San Francisco.Source
• Y CombinatorLaunch post: "We built the world's first agent-first firmware simulator"; Cloud Sim is "the first virtual devboard you can program and run entirely from your terminal" and needs only an MCU model and a compiled ELF; Pyrite can run locally in CI/CD or agent harnesses for select partners; the founders, formerly in firmware and hardware roles at Tesla, Neuralink, NXP and Onsemi, ask to hear from teams in automotive, robotics or aerospace. No traction or customers are disclosed.Source

Freeze a 1.0 API for the pytest fixture and run_firmware, publish to PyPI with semantic versioning, add a docs page with three recipes (UART expectation, register read, faulty-peer test) and link it from the homepage and /cloud-sim.

`pip install` plus a pytest fixture is a familiar, low-friction start, and a stable API is what lets teams put it in CI.

• Freezing the API too early

  Freeze only the small core; keep the rest experimental.

• #4 Fix the "coming soon" labels: the CLI is already documented and the Python SDK is on GitHub

• GitHubThe simantic-dev organization has 17 public repositories, all at 0 stars: `pippy` ("Test firmware without a board: Python SDK and pytest plugin", alpha 0.4.x, "not distributed on PyPI"); `embedded-ci-action` (a GitHub Action that submits firmware .elf files for simulation, with results in the dashboard's Embedded CI tab; no releases, used at @main); `examples` (good and faulty scripted peers per bus: GPS and RC links over UART, a barometer, power monitor and accelerometer over I2C, an IMU over SPI, DroneCAN and Ethernet; "No firmware is included"); and forks of Zephyr, QEMU and open-source flight-controller, e-reader, solar-car and student racing firmware.Source
• Your websiteHomepage: H1 "Real firmware. Simulated hardware."; Cloud Sim access is listed as HTTP API, TypeScript and MCP, with "Python" and "CLI" marked "Coming soon"; the AI firmware review section shows a sample review of an STM32F072RB blinky project; the hero visual shows I2C and RC rise-time waveforms; "Backed by Y Combinator"; no customers, logos or testimonials, and no list of supported microcontrollers.Source
• Your websiteDocs (/docs): the `sim` CLI installs with one curl command on macOS (Apple Silicon) or Linux x64, and on Windows only through WSL2; it needs Python 3.12+ with its shared library, and every run needs a Simantic account. The sample `sim models` output lists RP2040, STM32F072RB, STM32F401RE and "..."; the STM32H743 and STM32H753 parts are "modeled since sim 0.8" while other H7 parts are "not-modeled". "Usage reporting is required in this build and has no opt-out": each command reports its options, duration, OS and, for runs, the ELF size and SHA-256 (firmware and UART output are not sent).Source

Write one honest page per alternative: what each is best at (Renode's board breadth, QEMU's ubiquity, Wokwi's browser and classroom reach), where Simantic differs (determinism, virtual time, agent and MCP access, simulation-checked PR review, published validation) and how to move a test suite across. Date each page and cite sources.

Comparison searches come from engineers already choosing a tool. Honest pages earn trust and help AI assistants describe Simantic correctly.

• Seen as attacking open-source projects

  Credit them generously and state where they are the better choice.

• #8 Publish silicon-versus-simulation results per chip on the validation page

• News coverageAI Weekly (October 30, 2026): the engine was written from scratch in Rust rather than wrapping Renode or QEMU, citing development speed, performance and timing accuracy; the platform offers virtual dev boards by API, simulation-checked AI code review and CI that validates every commit; launch chips are STM32F0/F4/H7, ESP32-S3/C3 and RP2040, with new models arriving weekly; the company cites hardware validation rigs running around the clock; target uses include flight controllers, EVs, robotics and satellites.Source
• Competitor researchWokwi (homepage and pricing): "World's most advanced ESP32 simulator", running in the browser for Arduino, ESP32, STM32 and Raspberry Pi Pico; Community is €0 with unlimited simulations; Wokwi Pro is €20 per seat a month with "2000 monthly CI minutes", VS Code and JetBrains plug-ins and team billing.See the research Source
• Competitor researchRenode (Antmicro's platform page): an open-source emulation framework claiming 1200+ supported boards, 12+ CPU architectures and 800+ peripheral models, with public Zephyr and U-Boot test dashboards per board, integrations with GitHub Actions, GitLab and Jenkins, and paid services for peripheral modeling and CI setup.See the research Source
• Your websiteSitemap (14 URLs, checked November 9, 2026): the homepage, /cloud-sim, /pricing, /validation, /contact, /investors, /apply, /blog, /privacy, /terms and four docs pages (/docs, /docs/guide, /docs/pr-review, /docs/simantic-json). There are no supported-chip, CI, use-case, changelog or comparison pages, and the blog says only "We're working on it. Check back later."Source

Write a clear README for the MCP package (the tools it exposes, a config snippet, a 30-second demo GIF), submit it to the main MCP registries and directories, and add a /docs/agents page showing an agent writing, running and fixing firmware against Cloud Sim. Publish a template repo with simantic.json, CI and the MCP config ready to use.

Agent builders adopt tools that are one config line away. Being listed where they search is cheap distribution for the exact audience the launch names.

• Agent users burn credits quickly

  Default the MCP to short virtual timeouts and show cost per call.

• npmTwo packages: @simantic/cloud-sim (35 weekly downloads) and @simantic/cloud-sim-mcp (29 weekly downloads), the TypeScript SDK and MCP server linked from the homepage.Source
• Your websiteHomepage: H1 "Real firmware. Simulated hardware."; Cloud Sim access is listed as HTTP API, TypeScript and MCP, with "Python" and "CLI" marked "Coming soon"; the AI firmware review section shows a sample review of an STM32F072RB blinky project; the hero visual shows I2C and RC rise-time waveforms; "Backed by Y Combinator"; no customers, logos or testimonials, and no list of supported microcontrollers.Source
• Y CombinatorLaunch post: "We built the world's first agent-first firmware simulator"; Cloud Sim is "the first virtual devboard you can program and run entirely from your terminal" and needs only an MCU model and a compiled ELF; Pyrite can run locally in CI/CD or agent harnesses for select partners; the founders, formerly in firmware and hardware roles at Tesla, Neuralink, NXP and Onsemi, ask to hear from teams in automotive, robotics or aerospace. No traction or customers are disclosed.Source

Publish /security: exactly what leaves the machine for each product, retention periods, subprocessors, where reviews run, the firmware-storage switch, and the compliance roadmap. Offer a telemetry opt-out (or offline licence) for Enterprise and private-hosting builds, and a one-page security summary for procurement.

Regulated buyers move faster when the answers to their first questionnaire are already public. Turning "no opt-out" into an Enterprise feature gives a concrete reason to upgrade.

• Less usage data from big accounts

  Keep aggregate, opt-in reporting for Enterprise.

• Your websiteDocs (/docs): the `sim` CLI installs with one curl command on macOS (Apple Silicon) or Linux x64, and on Windows only through WSL2; it needs Python 3.12+ with its shared library, and every run needs a Simantic account. The sample `sim models` output lists RP2040, STM32F072RB, STM32F401RE and "..."; the STM32H743 and STM32H753 parts are "modeled since sim 0.8" while other H7 parts are "not-modeled". "Usage reporting is required in this build and has no opt-out": each command reports its options, duration, OS and, for runs, the ELF size and SHA-256 (firmware and UART output are not sent).Source
• Your websitePR reviewer docs (/docs/pr-review): mention @simantic-bot in a pull request and it builds the firmware, runs scenarios designed from the diff in the simulator and posts one review; it is "an on-demand assistant, not CI: nothing runs on a push"; "a pull request for any other MCU gets a static review, without simulation and never approved"; reviews draw on "$10 a month on the Community plan, $200 on Developer", shared with simulation runs, and are refused with less than $1.50 left; enterprise groups are billed as a group; reviews are private by default and can be shared by link; the diff, build output and simulator output are sent to the company's model provider.Source
• Your websitePricing page: Community ("For individuals getting started", no price shown, "$10 in monthly credits", 3 concurrent simulation runs, GitHub integration, "Sign up"); Developer ("For professional engineers", $100 a month or $1,000 a year, shown as $83.33/mo, "$200 in monthly credits", 10 concurrent runs, early access to simulation models); Enterprise ("Contact Us": unlimited API usage, unlimited concurrent runs and PR reviews, private hosting, custom subdomain and SSO, custom SLA). There is no FAQ and no explanation of what a credit buys.Source
• Competitor researchEmbedder (homepage): a Y Combinator-backed "autonomous firmware engineer" claiming 10,000+ developers; it tests on real silicon, probes and instruments rather than simulation; it states SOC 2 Type II and ISO 27001, with on-prem and air-gapped deployment options.See the research Source

Host sample ELFs per supported chip (blinky, UART hello, an I2C sensor read, a CAN node) and add `sim run --sample <name>` plus a "Run a sample" button in the dashboard. Pair each sample with its faulty-peer scenario from the examples repo so users see a firmware bug caught within minutes.

Time to first successful run is the activation metric for developer tools. Removing the toolchain step turns curious signups into users who have seen it work.

• Samples feel like toys

  Include one realistic sensor and CAN example per chip.

• #1 Publish one public list of supported microcontrollers, and link it from the homepage, Cloud Sim and pricing

• GitHubThe simantic-dev organization has 17 public repositories, all at 0 stars: `pippy` ("Test firmware without a board: Python SDK and pytest plugin", alpha 0.4.x, "not distributed on PyPI"); `embedded-ci-action` (a GitHub Action that submits firmware .elf files for simulation, with results in the dashboard's Embedded CI tab; no releases, used at @main); `examples` (good and faulty scripted peers per bus: GPS and RC links over UART, a barometer, power monitor and accelerometer over I2C, an IMU over SPI, DroneCAN and Ethernet; "No firmware is included"); and forks of Zephyr, QEMU and open-source flight-controller, e-reader, solar-car and student racing firmware.Source
• Y CombinatorLaunch post: "We built the world's first agent-first firmware simulator"; Cloud Sim is "the first virtual devboard you can program and run entirely from your terminal" and needs only an MCU model and a compiled ELF; Pyrite can run locally in CI/CD or agent harnesses for select partners; the founders, formerly in firmware and hardware roles at Tesla, Neuralink, NXP and Onsemi, ask to hear from teams in automotive, robotics or aerospace. No traction or customers are disclosed.Source
• Your websiteCloud Sim page (/cloud-sim), the target of the homepage "Try Cloud Sim" button, checked twice on November 9, 2026: its whole body is "Introducing Cloud Sim" and "Cloud Sim lets you run your firmware from anywhere, with minimal setup." It names no chip and has no code sample or steps; the only next step is the Dashboard link.Source

When the bot infers a working configuration, offer "@simantic-bot add-config", which opens a pull request containing the detected simantic.json (mcu, build system, ELF path, a smoke `expect`). When detection fails, the review explains which field is missing and links to the chip page.

One click to a correct config makes every later review a full simulated review, which is when the product shows its value and uses credits.

• Wrong inferred config

  Open it as a PR for the user to review, never a direct commit.

• Your websitesimantic.json docs: only `mcu` is required; without the file "the reviewer detects the build and MCU itself and ends its review by suggesting you commit a simantic.json"; supported build systems are CubeMX make, make, CMake, pico-sdk, ESP-IDF and Zephyr; a review is static and "can never be an approval" when the MCU is unsupported, the toolchain is missing, the build fails or the firmware never runs.Source
• Your websitePR reviewer docs (/docs/pr-review): mention @simantic-bot in a pull request and it builds the firmware, runs scenarios designed from the diff in the simulator and posts one review; it is "an on-demand assistant, not CI: nothing runs on a push"; "a pull request for any other MCU gets a static review, without simulation and never approved"; reviews draw on "$10 a month on the Community plan, $200 on Developer", shared with simulation runs, and are refused with less than $1.50 left; enterprise groups are billed as a group; reviews are private by default and can be shared by link; the diff, build output and simulator output are sent to the company's model provider.Source

Launch a self-serve Team plan: per-seat pricing, a pooled credit balance, one GitHub organization install for Simantic Bot and CI, higher concurrency, invoices and an admin view of usage. Keep Enterprise for private hosting, SSO and SLAs.

Firmware work is done in teams, and a pooled, self-serve plan captures them before they need procurement, raising revenue per account.

• Cannibalizes Enterprise

  Keep private hosting, SSO and SLA Enterprise-only.

• #3 Show what $10 and $200 of credits actually buy, and label Community as free

• Your websitePricing page: Community ("For individuals getting started", no price shown, "$10 in monthly credits", 3 concurrent simulation runs, GitHub integration, "Sign up"); Developer ("For professional engineers", $100 a month or $1,000 a year, shown as $83.33/mo, "$200 in monthly credits", 10 concurrent runs, early access to simulation models); Enterprise ("Contact Us": unlimited API usage, unlimited concurrent runs and PR reviews, private hosting, custom subdomain and SSO, custom SLA). There is no FAQ and no explanation of what a credit buys.Source
• Your websitePR reviewer docs (/docs/pr-review): mention @simantic-bot in a pull request and it builds the firmware, runs scenarios designed from the diff in the simulator and posts one review; it is "an on-demand assistant, not CI: nothing runs on a push"; "a pull request for any other MCU gets a static review, without simulation and never approved"; reviews draw on "$10 a month on the Community plan, $200 on Developer", shared with simulation runs, and are refused with less than $1.50 left; enterprise groups are billed as a group; reviews are private by default and can be shared by link; the diff, build output and simulator output are sent to the company's model provider.Source
• Competitor researchWokwi (homepage and pricing): "World's most advanced ESP32 simulator", running in the browser for Arduino, ESP32, STM32 and Raspberry Pi Pico; Community is €0 with unlimited simulations; Wokwi Pro is €20 per seat a month with "2000 monthly CI minutes", VS Code and JetBrains plug-ins and team billing.See the research Source

Pick one board-level scenario with clear value, such as I2C pull-up and bus-capacitance checks, or reset and brown-out behaviour, and couple the SPICE model to the MCU simulation for that scenario only. Validate it against a real board, publish the results, and sell it as an add-on to Developer, Team and Enterprise.

Joint firmware and electronics simulation is a gap neither firmware-only simulators nor hardware-first agents fill, and it fits the regulated buyers who pay most.

• Research takes longer than planned

  Ship one narrow, validated scenario before broadening.

• Slow simulation

  Simulate only the nets that the scenario needs.

• #8 Publish silicon-versus-simulation results per chip on the validation page

• HiringLead Simulation Researcher (Electronics / Firmware), Waterloo or San Francisco, $200K-$300K and 2.00%-5.00% equity, 6+ years: to "lead Simantic's efforts to develop an electronics simulation platform based on SPICE and Xyce for agentic AI use", prototyping hardware to check that the simulation physics matches real-world behavior. The listing describes a team of 4.Source
• Your websiteHomepage: H1 "Real firmware. Simulated hardware."; Cloud Sim access is listed as HTTP API, TypeScript and MCP, with "Python" and "CLI" marked "Coming soon"; the AI firmware review section shows a sample review of an STM32F072RB blinky project; the hero visual shows I2C and RC rise-time waveforms; "Backed by Y Combinator"; no customers, logos or testimonials, and no list of supported microcontrollers.Source
• Your websiteGuide (/docs/guide): examples name STM32F401RE, STM32H753IITX, STM32G474RE, STM32F767ZI, NRF52840QIAA and ESP32-C3, C6 and S3, and point to `sim models` for the list; modeled buses include UART, I2C, SPI, CAN FD, BLE, 802.15.4, Ethernet, Wi-Fi, SD/MMC, USB, GPIO, timers and DMA; Python "peers" stand in for sensors and other parts; "`--timeout` is virtual seconds".Source
• Your websiteValidation page: principles such as "Let real hardware be the reference", "Look beyond a successful boot", "Make failures part of the test" and "Show the evidence. Name the boundaries.", and "We are building toward a validation standard that firmware simulation has not seen before." It names no chips and shows no numbers or results; the call to action is "Talk to the team".Source

Pitch chip makers' developer-relations teams and large distributors a co-branded "try it now" page for a new or popular part: a hosted sample, a Cloud Sim run in the browser and a path to Simantic for testing. Charge for priority modeling and validation of their parts, or run it as a lead-sharing partnership.

It puts Simantic in front of engineers at the moment they evaluate a chip, under a trusted vendor's brand, and funds the modeling roadmap.

• Vendors demand accuracy proof

  Lead with the published validation report (idea 8).

• Long partner cycles

  Start with a distributor or a smaller vendor.

• #8 Publish silicon-versus-simulation results per chip on the validation page

• News coverageUniversity of Waterloo news (July 31, 2026): the founders met the problem in co-op roles where engineers often waited weeks or months for physical devices; the company started in September 2025 and was accepted into Velocity's startup program and Y Combinator's Fall 2026 batch; it has raised about $600,000 USD; the founders met customers, design partners and investors in San Francisco.Source
• News coverageAI Weekly (October 30, 2026): the engine was written from scratch in Rust rather than wrapping Renode or QEMU, citing development speed, performance and timing accuracy; the platform offers virtual dev boards by API, simulation-checked AI code review and CI that validates every commit; launch chips are STM32F0/F4/H7, ESP32-S3/C3 and RP2040, with new models arriving weekly; the company cites hardware validation rigs running around the clock; target uses include flight controllers, EVs, robotics and satellites.Source
• Your websiteDocs (/docs): the `sim` CLI installs with one curl command on macOS (Apple Silicon) or Linux x64, and on Windows only through WSL2; it needs Python 3.12+ with its shared library, and every run needs a Simantic account. The sample `sim models` output lists RP2040, STM32F072RB, STM32F401RE and "..."; the STM32H743 and STM32H753 parts are "modeled since sim 0.8" while other H7 parts are "not-modeled". "Usage reporting is required in this build and has no opt-out": each command reports its options, duration, OS and, for runs, the ELF size and SHA-256 (firmware and UART output are not sent).Source

Define one productised offer: an annual on-prem Pyrite licence with an offline mode, a validation pack for the customer's chips, an onboarding sprint to wire it into their CI, and a support SLA. Sign three design partners at a discount in exchange for case studies, then publish the offer.

Regulated teams pay for local deployment and evidence, and a licence turns individual pilots into larger annual contracts.

• Custom work per customer

  Keep the offer fixed and charge for extras.

• Long procurement

  Start with a paid pilot inside an existing budget.

• #8 Publish silicon-versus-simulation results per chip on the validation page
• #15 An Enterprise data and telemetry page, with a telemetry opt-out for private hosting

• Y CombinatorCompany profile: Fall 2026 batch, founded 2025, team of 4, Waterloo, Canada; products are Cloud Sim (a cloud virtual dev board), Simantic Bot (an AI reviewer that runs firmware on a simulated microcontroller) and Pyrite, "a firmware simulation model available to select partners".Source
• Y CombinatorLaunch post: "We built the world's first agent-first firmware simulator"; Cloud Sim is "the first virtual devboard you can program and run entirely from your terminal" and needs only an MCU model and a compiled ELF; Pyrite can run locally in CI/CD or agent harnesses for select partners; the founders, formerly in firmware and hardware roles at Tesla, Neuralink, NXP and Onsemi, ask to hear from teams in automotive, robotics or aerospace. No traction or customers are disclosed.Source
• Your websitePricing page: Community ("For individuals getting started", no price shown, "$10 in monthly credits", 3 concurrent simulation runs, GitHub integration, "Sign up"); Developer ("For professional engineers", $100 a month or $1,000 a year, shown as $83.33/mo, "$200 in monthly credits", 10 concurrent runs, early access to simulation models); Enterprise ("Contact Us": unlimited API usage, unlimited concurrent runs and PR reviews, private hosting, custom subdomain and SSO, custom SLA). There is no FAQ and no explanation of what a credit buys.Source
• Your websiteValidation page: principles such as "Let real hardware be the reference", "Look beyond a successful boot", "Make failures part of the test" and "Show the evidence. Name the boundaries.", and "We are building toward a validation standard that firmware simulation has not seen before." It names no chips and shows no numbers or results; the call to action is "Talk to the team".Source

Serve the hero board image as AVIF/WebP at the displayed sizes with a high fetch priority, self-host the fonts with font-display swap, and preload the main font. Recheck PageSpeed afterwards.

A faster first paint on slower phones protects the first impression for launch-driven traffic at almost no cost.

• Image quality loss on the hero

  Compare at 2x density before shipping.

• PageSpeedGoogle PageSpeed (homepage, tested this week): mobile score 92, desktop 100; real visitors pass Core Web Vitals (field LCP 1.06 s, CLS 0); in the lab phone test the largest element, the hero circuit-board image, paints at 2.9 s; images are 1,458 KB of a 1,555 KB page; render-blocking requests (Google Fonts) cost about 1.2 s; one colour-contrast accessibility issue.Source

Let users add a README badge ("Simulated on STM32F401RE: passing") that links to a public summary of the latest review or CI run, with a small "Try Simantic on your firmware" link. Make it opt-in per repository, and show only the summary unless the owner shares more.

Badges are a familiar open-source growth loop, and each one is a credible endorsement from a working engineer in place of the logos Simantic doesn't yet have.

• Exposing private details

  Opt-in only, public repos only, summary by default.

• #10 Run the bot on well-known open-source firmware and publish the real bugs it finds

• Your websitePR reviewer docs (/docs/pr-review): mention @simantic-bot in a pull request and it builds the firmware, runs scenarios designed from the diff in the simulator and posts one review; it is "an on-demand assistant, not CI: nothing runs on a push"; "a pull request for any other MCU gets a static review, without simulation and never approved"; reviews draw on "$10 a month on the Community plan, $200 on Developer", shared with simulation runs, and are refused with less than $1.50 left; enterprise groups are billed as a group; reviews are private by default and can be shared by link; the diff, build output and simulator output are sent to the company's model provider.Source
• Your websiteHomepage: H1 "Real firmware. Simulated hardware."; Cloud Sim access is listed as HTTP API, TypeScript and MCP, with "Python" and "CLI" marked "Coming soon"; the AI firmware review section shows a sample review of an STM32F072RB blinky project; the hero visual shows I2C and RC rise-time waveforms; "Backed by Y Combinator"; no customers, logos or testimonials, and no list of supported microcontrollers.Source
• GitHubThe simantic-dev organization has 17 public repositories, all at 0 stars: `pippy` ("Test firmware without a board: Python SDK and pytest plugin", alpha 0.4.x, "not distributed on PyPI"); `embedded-ci-action` (a GitHub Action that submits firmware .elf files for simulation, with results in the dashboard's Embedded CI tab; no releases, used at @main); `examples` (good and faulty scripted peers per bus: GPS and RC links over UART, a barometer, power monitor and accelerometer over I2C, an IMU over SPI, DroneCAN and Ethernet; "No firmware is included"); and forks of Zephyr, QEMU and open-source flight-controller, e-reader, solar-car and student racing firmware.Source