Build log
The build, dated.
Gyro Suite has not been released, so there is no release history to show you yet. There is a build, and it is moving fast. This is the dated record of what has been built since the first install on 15 August 2026, written from the project's own log rather than from a marketing plan.
Costing, pricing rules and the owner's console
- Receipts, deliveries, transfers, adjustments and returns are costed by each item's own method, FIFO, average or standard, inside one journal entry
- Lots and serial numbers on the trade documents, first-expired-first-out proposed before despatch, and a one-screen recall
- A pricing rules engine that explains every price it gives, with a margin floor and a discount ceiling that can hold a quote for a named signer
- Tax rules and fiscal positions that say in a sentence why a line carries its tax, with withholding and reverse charge posted on both sides
- Multi-level recipe costing in manufacturing, and a production plan that raises each work order and purchase request exactly once
- Every list exports as CSV, an Excel workbook or a PDF, with long ones prepared in the background
- Failed jobs, the application log and scheduled work as screens for the person who owns the installation
- Leads by web form, sales mailbox and import; ticket templates; an activity calendar; eight country charts of accounts
- At the end of this work: 397 staff screens and 22,974 automated tests, every one run on both database engines
Commerce, communication and a second test engine
- The licence engine, the online store with card payment, the AI assistant that uses your own provider key, and the installable mobile app
- Outgoing email with a real test message, a webmail client with a shared team inbox, and a website builder that publishes
- SEPA direct debit and credit transfer, single sign-on, and the statutory exports FEC, DATEV and SAF-T
- A visual print designer: drag blocks into the header, body and footer of any document and watch a live preview
- Telephony, EDI, configure-price-quote, recruitment interviews with scorecards, and the till working offline
- Email campaigns that send, configurable sales pipelines, project plans edited on the Gantt, and fixed assets through to disposal
- Personal and team booking links, a live-chat widget for your website, appraisals and onboarding
- A second full test run on MariaDB, the database the product ships on, green for the first time on 18 September
The ledger, the stock engine and the factory floor
- The double-entry ledger the product is sold on: immutable postings, period locks and statements that tie out
- Recurring billing, credit notes, quotations, the financial report pack, and branches inside a company
- The inventory engine and its immutable stock ledger, and the reporting layer above it
- The guided installer, scheduled backups, the health page and the manual
- Counter sales posting to the books, and batch and serial tracked stock inside the ledger
- Module fault isolation and a recovery console, so one broken module cannot take the installation down
- Material requirements planning, subcontracting and the shop floor
- The customer portal, payroll runs that post one balanced journal, and bank reconciliation
The first install, and a first screen for every module
- The first working installation on an ordinary shared cPanel account, with no Composer and no command line on the server
- The shared-hosting floor measured, not assumed: a queue drained by a one-minute cron, a migration that survived eleven interruptions, a 5,000-row export in the background
- A 50-row list rendering in about 40 milliseconds against 10,000 rows, on that same shared account
- A first working screen for all 43 modules, the theme, and four panel layouts
- Invoices, quotations and statements as PDFs, with a print template per company and a live preview
- The first email the product sent by itself: an invoice, to a customer
How to read this page
Built is not the same as finished. Everything above exists in the build and is covered by automated tests. Nothing is called done until somebody has opened the screen and used it, and a good deal of that work is still ahead. The roadmap says what.
When version 1.0 ships, this page becomes the changelog: every release with its date, its version and what changed, with security fixes marked. Security fixes will be free on every version, always, whether a subscription is current or not.
See what is left.
The roadmap says what stands between today's build and version 1.0, and what we have decided not to build at all.