Installer
Runs an engineering installation as a git project: description, checks, emulation, building and flashing devices, handover to the customer. Commands it opens: 599. 3,000 NC a year.
weld builds the program for your installation
weld is a command line and a window for projects made of equipment and clouds. A customer buys the modules needed, and the factory builds a program with only those.
Modules
Each module opens its own commands. The core (projects, the computer check, the window, the Weld Vibe assistant) is part of every customer's program.
weldctl modules
Operator
Work on an installation that is already handed over: allowed actions, recovery, telemetry, analysis, manual tasks and updating the body. Commands it opens: 456. 2,000 NC a year.
Infrastructure
Kubernetes clusters and applications from git: on one machine, in a local VM and in clouds, with moves between them. Commands it opens: 155. 3,000 NC a year.
Agro
Crop profiles, nutrient solutions, rooms and growing cycles on the common control core. Commands it opens: 567. 3,000 NC a year.
Power
The power system of a site: supply schemes, load and redundancy calculation, checks against standards. Commands it opens: 366. 2,500 NC a year.
Devices
The device catalogue, protocols, the topology of field devices and firmware at device level. Commands it opens: 366. 2,500 NC a year.
Science
Model passports, parameter sets, ranges of applicability and the solvers of the science root, with no industry commands. Commands it opens: 0. 1,500 NC a year.
Viewer
Read-only viewing and diagnostics: the monitor, diagnostics, emulation without writing. Commands it opens: 0. 500 NC a year.
The price is a proposal for now; the owner sets the final one. The set builder in the cabinet adds up the total.
Build your set
Tick the modules: the yearly total is added up at once.
What you can build
Systems a developer builds on weld as a project. Each names the modules it needs.
A brewery or a bottling line
Each brew runs as an ISA-88 batch, the event log collects the batch record, and genealogy shows which lots of malt and hops a bottle was made from.
Modules: Operator, Devices, and Installer for setup on site
A bakery
Dough batches, flour use by lot, ovens with temperature sensors and a shift report from the event log.
Modules: Operator, Devices
A compressor station
The resident agent holds pressure to a setpoint schedule and puts the station into safe mode on a fault.
Modules: Operator, Devices, Power
A server room
The power scheme from the inlet to the rack, N+1 redundancy, cooling with setpoints and clusters on the racks.
Modules: Power, Devices, Infrastructure, Operator
A microgrid with storage
Modes grid, storage and emergency, a log of switchovers and a check that the reserve lasts for a given time.
Modules: Power, Devices, Operator
A pumping station
Pumps, levels and pressure, emergency interlocks and an event log for the report to the regulator.
Modules: Devices, Operator, Power
A cold store
An event log with a hash chain is the proof that the cold chain was not broken; batches of goods are traced by lot.
Modules: Devices, Operator
A company cloud
A development workshop with git and CI, a Kubernetes training cluster or a multi-tenant platform: all of them are already described as ready setups.
Modules: Infrastructure, Operator
A laboratory
Instruments with passports and calibration dates, a measurement log that records where each number came from.
Modules: Science, Devices, Operator
A greenhouse or a grow box
The crop profile is data, and control runs on the common core.
Modules: Agro, Devices, Operator
For developers
We build our own applications the way third-party developers will: a weld project, with data instead of code for the industry.
A customer project
A developer takes a blueprint from the catalogue, fills in the customer's data, checks the project on emulators and hands it over with project transfer and project target handover. After the handover the project and the data belong to the customer.
Weld GUI
A page written in HTML and CSS becomes a desktop window, a terminal page or a screen on a board. The weldctl window is already built on it; a separate module for your own interfaces is in preparation.
Weld Vibe
An offline assistant with no neural network turns requests in Russian and English into weldctl commands and knows only the commands of your set. It belongs to the core; today it is a separate program, and building it into weldctl is planned.
Event log and batches
An application builds its process logic on the event log and the batches of the process domain. Declaring the modules it needs in weld.yml is in preparation: weld will refuse to install the application where they are missing.
Security
Each customer gets a program of their own, not one build for everyone.
A body of your own
The body is built for the modules bought. The code of the other modules is physically absent, which is checked at build time, and each customer has their own obfuscation and watermark.
Sealed to the machine
The body is encrypted and opens only on the customer's installation; the open body is never written to disk. A file carried to another machine does not open. Today this works on Linux.
Without a network
The program works offline to the end of the lease: thirty days and thirty more as a reserve. After that new work is refused with TERM-001, and the protective functions stay.
Seats and revocation
The number of machines per right is limited by seats. Any right is revoked with one button, and after a revocation the earlier body is no longer accepted.
How to buy and how updates arrive
An order goes through the cabinet. Automatic issue after payment through Pay is being prepared together with the release rails; for now the owner issues the set.
- Build the set above and sign in with Naasson ID.
- The owner confirms the order, and the factory builds your body and issues the right to the set.
- Install weldctl with one command from the Install page and register the installation.
- Updates arrive in rings: the pilot first, then early customers, then everyone else. You get an email and install the update yourself; there is no automatic update.
- Version
- 1.0.4
- Platforms
- Linux x86-64
- Channel
- stable, signed
Questions
How much does it cost?
The yearly price of each module is on its card, and the builder adds up the set. The prices are proposals for now; the owner sets the final ones.
What happens when the work term ends?
New work is refused with TERM-001. Installation control and protective functions keep running. The owner renews.
And when the update term ends?
New builds are not downloaded. The installed one keeps working.
On how many computers?
As many as the right has seats. Each device takes one; when all are taken, enrollment answers ENR-003. A new computer enrolls again, and the owner frees the old seat.
Is there macOS or ARM?
Not in the first release.