Core concepts

A short mental map of Subaya before you go deeper.

CLI-first

The suya CLI is the primary interface — for humans, AI agents, and CI. The web console at subaya-dev.com is for results: waveforms, reports, project management, and review. The thinking — design, simulation, validation — happens through the CLI and the agents that drive it.

suya is to subaya-dev.com what gh is to github.com.

Tenancy: org → workspace → project

• Organization — your account’s top-level tenant. Billing, members, and licenses live here.
• Workspace — a grouping of projects within an org (e.g. a team or a product line).
• Project — the unit of work: a typed (fpga or embedded) design with its own requirements, simulations, repo, and phase.

Project types

Type	For	Toolchains
fpga	RTL / FPGA designs	RyuSim, Verilator, Icarus, Questa, Vivado xsim, Quartus
embedded	MCU firmware (e.g. STM32)	CubeMX pin-planning, Renode

Phases

Every project moves through phases that shape the UI and the available tools:

Concept → Plan → Implement → Simulate → Verify

Get or set the current phase with suya project phase.

Cloud-hosted tools

Heavy tools run on Subaya’s backend, not your laptop: Quartus, RyuSim, Renode, BitCrucible, and a headless CubeMX engine. You drive them through the CLI and pay only for the compute seconds you use — see Billing & usage.

Authentication

Two modes, covered in Authentication & API keys:

• SUBAYA_API_KEY — for agents and CI, no browser.
• suya auth login — OAuth browser flow for human developers.