AI-assisted Design Review in Allspice with DRCY
Design reviews should be about architecture and tradeoffs, not hunting for a swapped pin or an out-of-spec supply rail. DRCY, Allspice's AI design review agent, handles those checks inside the review itself, so engineers can spend their time on the decisions that need them.
Here's a quick tour of how an AI-assisted review works in Allspice, plus the newest DRCY features.
Prefer to read? The steps below follow the video.
Get your design into Allspice Hub
Allspice Hub is a browser-based platform where hardware teams store and review design changes. It works with any ECAD tool. Drag and drop your project, or commit and push with Git.
Allspice parses your schematic and PCB files right away, so reviewers can compare changes visually instead of digging through exports.
Add DRCY as a reviewer
Every review starts on the Conversations page. That's where you capture intent, add reviewers, and coordinate feedback.
Add DRCY alongside your human reviewers and it kicks off an AI review automatically. No separate tool, no export, no report to chase down.
When DRCY finishes, it posts its findings into the review as an interactive summary table. You can search and filter findings, post the ones you want to the conversation, or export the full set.
Datasheet-backed findings
DRCY automatically retrieves datasheets and links them to each component, including ones you upload or keep in a datasheets folder in the repo. If one is missing, DRCY tells you. Upload it in the review and rerun the analysis without leaving the page.
With that context, DRCY catches issues like:
- Missing or incorrect pin connections
- Out-of-spec power supply connections
- Incompatible component configurations
- Unconventional pin reuse the datasheet allows, but that's worth a second look
Filter for errors to see the highest-severity findings first. In one example, DRCY flagged microcontroller U11A: the net named DATA_IN was wired to the MCU's data output pin. The comment lays out what DRCY observed in the schematic, the requirement from the datasheet, the consequence, the evidence, and a suggested fix.
Click the snippet in the comment to jump straight into the design review. You see the component, the recent changes that caused the issue, and the supporting evidence from the rest of the design.
Every finding starts a conversation
If a finding needs a fix, escalate it to an Allspice issue and track it in the repository's issue tracker.
Want to dig deeper first? Open DRCY Chat straight from any DRCY review comment or issue. The comment's context comes along, so you can ask follow-ups like "Why did you flag this?" or "What other parts on this net could be affected?"
You can also upload supporting documents, like specs, requirements, or application notes as PDFs or Word files, and DRCY will use them in its answers.
Teach DRCY how your team works
Add a DRCY.md file to your repository with your organization's design standards, conventions, and formatting preferences. DRCY Chat follows them in every session.
The bottom line
With DRCY, issues surface early, reviews focus on decisions instead of cleanup, and sign-off carries real confidence. DRCY won't replace engineers. It protects their time by handling the checks nobody should have to repeat, so your team can focus on building better designs and shipping with confidence.
