Your account, team and licences
A workspace holds your designs, the people you invite, the licences bought for each design and the credits the AI assistant uses.
Signing in and the designs list
Press Start designing on the home page, or open /designs/. Sign in with your Google account, or with an email address and a password. The first sign-in makes your workspace, with you as its owner; every design, team member, licence and credit belongs to the workspace, and nothing is kept in the browser.
- New design asks for a name and opens the editor on an empty canvas. The name is edited in the editor's top bar.
- Open editor returns to a design; Clone copies one with its current flow as version 1.
- The list view shows who made each design, the Files given to the AI assistant for it (a manual, a spreadsheet, a PLC program file; each opens from there) and when it was last updated.
- Delete moves a design to the Trash, where it stays for 30 days and can be restored; after 30 days it is removed for good, with its history and bundles.
The team and its roles
The owner invites others from the Team page by email address. An invitation arrives as an email with a link (or the link is shown, to pass on by hand) and the person signs in with that address. Each member has one role:
| Role | Can |
|---|---|
| Owner | Everything: every design, inviting and removing members, buying licences and credits, the credit usage report. The person who created the workspace. |
| Admin | Everything except inviting members and purchasing. |
| Designer | Make designs and edit the ones they created. Other members' designs open read-only. |
A member who is removed keeps nothing; the designs they made stay in the workspace. Someone invited into more than one workspace switches between them from the profile menu.
Licences per design
A trial runs a design on a device for seven days. To run it for good, the owner buys a licence for that design, with a quantity: one licence per device it will run on. The price follows the design's number of IO tags:
| Design size | Per device, INR | Per device, USD |
|---|---|---|
| Up to 100 IO tags | ₹5,000 | $50 |
| Up to 250 IO tags | ₹10,000 | $100 |
| Up to 500 IO tags | ₹18,000 | $175 |
| More than 500 IO tags | Contact sales | Contact sales |
- Buy licence is in the editor's Download Design sheet, and on the design page. Choose the quantity and the currency (INR or USD), and pay; the licences appear at once. When a promo code has been issued for your workspace, a box for it appears there too, with the percentage it takes off.
- Each activation of a purchased licence takes one of its devices, bound to that machine's device code. When every one is taken, the sheet offers Buy licence again, or move a licence from a device you name, twice a year per licence on your own, beyond that by writing to support.
- A licence belongs to the design it was bought for and to its IO-tag tier: editing the design is free as long as it stays within the tier, and a design that grows past it needs a licence of the next tier. Activation and the licence has what happens on the device.
The AI assistant and credits
The AI button in the editor's top bar opens the assistant in a pane beside the canvas, like the properties pane. It is built on Claude, and it does three things:
- Answers questions about Modbus, the other protocols, the editor and the runtime, in a conversation kept with the design.
- Extracts a device from a manual, data sheet, register map spreadsheet, PLC program file or a photo of a register table dropped into the chat: the name, the connection, and the tags with their addresses, data types and scaling. You review the result, then add it to the Device library or straight onto a node.
- Changes the design on request: add a device, wire it to an output, set a deadband, rename tags. The change is shown first as a preview with the touched nodes marked; Accept applies it as one step you can undo, Cancel leaves the design as it was. The assistant works from the design you have open and the same rules the editor validates with.
Every request costs credits, metered by how much is sent to the model and how much comes back; a file is charged for what the model reads of it. Credits belong to the workspace and are bought by the owner on the Credits page, in packs; a new workspace starts with a small balance to try the assistant. The owner and the admins see who used what on the credit usage report from the profile menu: each request with the member, the date and time, the feature and the credits it took.