The AI-assisted design platform that captures your requirements and turns them into ready-to-use schematics.
THE SYSTEM
CELUS carries a design from a plain-language requirement to a reference schematic and a bill of materials. Every layer below feeds the same flow, so what an engineer starts in a sentence arrives as a structured starting point in their EDA tool.
Seven layers, from the models that reason to the governance that makes them safe to connect.
01
Foundation models
Large language models supply the reasoning. On their own they will name a plausible component and stop. Every layer above this one exists to turn that reasoning into a design that holds up in an EDA tool.
MODEL OUTPUT, UNGROUNDED
No live data
Orchestrator
PLANS AND DELEGATES
Design Assistant
Sourcing
Review
02
Agentic harness
The orchestration layer. One agent talks to the engineer while an orchestrator delegates to specialists, each with its own tools and live data. It handles tool routing, control flow and model selection, runs specialists in parallel, and re-resolves the design when something it depends on changes.
03
Data and integrations
MCP connectors bring live product data from component manufacturers and distributors: specifications, interfaces and pin functions, packages and footprints, lifecycle status and current availability. Designs hand off to Altium, KiCad, Eagle and Siemens with the schematic, bill of materials and footprints attached.
LIVE PRODUCT DATA
Specifications
Pin functions
Footprints
Lifecycle
Availability
MCP connectors
HANDS OFF TO
Altium
KiCad
Eagle
Siemens
The requirement
The architecture so far
The component library
Choices already made
EACH RESOLVE STARTS FROM ALL OF IT
04
Context and knowledge
The requirement, the architecture decided so far, the component library and the choices already made are layered into every agent action. The platform picks up where the last resolve left off instead of starting from a blank sheet.
05
Design capabilities
Requirement capture in plain language. Block diagrams from intent. Component selection resolved function by function. Reference schematics and a bill of materials as a structured starting point. Review that checks the design against the requirement it came from.
Requirement capture in plain language
Block diagrams from intent
Component selection per function
Reference schematic and bill of materials
Review against the original requirement
DESIGN STUDIO
Design an ESP32-S3 audio board…
EMBEDDED ON A PARTNER SITE
The same agent, on a manufacturer’s product pages and reference libraries.
06
Products and interfaces
Design Studio is where engineers brief the platform and take the result into their EDA tool. The same agent can be embedded on a manufacturer’s product pages and reference libraries, so engineers get design help without leaving the site they are already on.
07
Security and governance
You choose what is exposed and in how much detail. Connections authenticate through standard OAuth and can be revoked at any time. A partner catalog is never repackaged for other vendors on the platform, and engineer project data stays with the engineer.
You choose what is exposed, and in how much detail
Standard OAuth, revocable at any time
No catalog is repackaged for other vendors
Engineer project data stays with the engineer
SOC 2 Type II
UNVERIFIED
ISO 27001
UNVERIFIED
ISO 42001
UNVERIFIED
GDPR
UNVERIFIED
PLACEHOLDER: I did not assert any certification. Confirm with security and legal which of these CELUS actually holds, delete the rest, and only then publish this band.
An intelligent electronics design platform that seamlessly automates component search, schematic generation, and EDA handover.
© Copyright 2026 CELUS · All rights reserved.
Socials
Twitter (X)





