BUS Core

BUS Core — Free Download. Small batch production control
BUS Core is a local production management program for workshops that build physical products in small batches. It replaces spreadsheets and paper logs with an SQLite database that calculates real production costs, maintains complete inventory audit trails, and records every manufactured batch. The tool is designed for operators in custom fabrication shops, makerspaces, repair and prototyping workshops who require precise material and per‑batch cost control.
★★★★★
5.0(2 ratings)

Download BUS Core (Official links)
File size: 32.6 MB
The latest version of BUS Core is: 1.4.2
Operating system: Windows
Languages: English
Price: $0.00 USD

  • Batch inventory control. Records materials and consumables using metric units (grams, millimeters, milliliters, each) with batch numbers, purchase dates, and cost per batch. The system maintains full traceability of every receipt and issue, preventing stock drift and enabling location of specific material batches during production.
  • FIFO cost calculation. Applies first‑in, first‑out method to value material consumption. Each time a product is manufactured, the system takes the cost of the oldest available batches, reflecting real historical production cost and avoiding distortions from supplier price fluctuations.
  • Recipes or blueprints. Defines the structure of each product by specifying exact quantities of required materials. The function stores recipe versions, allows component modifications, and automatically calculates standard product cost based on current batch prices of each material.
  • Manufacturing run logging. Documents each produced batch with date, quantity, responsible operator, and consumed materials. The system validates stock availability before starting the run and automatically deducts materials from inventory upon batch completion.
  • Real cost vs selling price comparison. For each assembled product, the function displays the calculated cost based on materials consumed in that specific batch and compares it with the established selling price. Enables per‑batch margin analysis and detection of cost deviations.
  • Vendor management with price history. Stores supplier information including historical purchase prices per material. The function allows querying price evolution and selecting optimal supplier for each restocking action based on actual previous purchase data.
  • Production ledger and full audit trail. Maintains an immutable record of all inventory movements: receipts by purchase, issues by manufacturing consumption, and adjustments for shrinkage. Each transaction includes a timestamp and reference to the production or purchase batch, enabling detailed retrospective audits.
  • Local SQLite database without telemetry. All information resides in an SQLite file on the user’s machine. No external servers, no data collection, no mandatory internet connections. The operator retains complete ownership of production data.
  • Native Windows support with Docker option. The application runs as a native executable on Windows systems without additional dependencies. For Linux or macOS environments, a Docker configuration is provided that runs the same database and manufacturing engine, maintaining file compatibility.
  • Encrypted database backups. Includes function to export the complete database with optional password encryption. Backups can be restored on any BUS Core installation, ensuring operational continuity in case of main equipment failure.
  • Purchase batch logging. Allows entry of each purchase order with its material lines, received quantity, unit cost, and date. The system automatically assigns a purchase batch number and updates inventory with the recorded cost, maintaining traceability from supplier invoice to finished product.
  • Pre‑manufacturing stock validation. Before authorizing a production run, the function checks availability of all required materials according to the recipe. If any material has insufficient stock, the system rejects starting the batch and identifies the deficient material with required and available quantities.
  • Per‑product and per‑batch cost query. Displays material cost of a specific product calculated with FIFO on current batches, as well as actual cost of historical batches already produced. The function breaks down each material with its unit cost and quantity consumed in that specific batch.
  • Spreadsheet data import. Provides tool to import material lists, initial inventory, and recipes from CSV or Excel files. The function validates data structure and assigns unique identifiers, reducing initial system configuration time.
  • Production ledger export. Generates complete report of all inventory movements and manufacturing runs in CSV format. The exported ledger can be used for external accounting reconciliation or cost analysis in spreadsheet tools.

The development history of BUS Core began in 2022 when a custom fabrication workshop in Canada documented its production processes using a combination of spreadsheets and manual records. Facing the lack of local, affordable, subscription‑free solutions, the workshop technical team decided to build its own management system. The first functional version was written in Python with an SQLite database, specifically designed for small‑batch workflow. The primary developers are part of True Good Craft, a Canadian company focused on low‑volume manufacturing tools. The source code was released under the AGPLv3 license in 2023, allowing other workshops to use, modify, and run the system without dependence on cloud services. The main programming language is Python for the production logic engine and SQLite storage, supplemented with shell scripts for Windows and Docker deployment.


Alternatives to BUS Core:

Changelog

Version: 1.4.2
  1. BUS Core 1.4.2 is a maintenance release focused on security, release governance and analytics operability; it adds no new product domain and does not widen the data BUS Core sends.
  2. Reviewed UI paths now build the DOM with text-safe methods instead of unsafe HTML interpolation, backed by regression tests against hostile payloads.
  3. Configured runtime roots are now the authoritative source for capability, secret, settings, database and configuration state.
  4. Reviewed, hash-locked dependency graphs for runtime, testing and fuzzing on Windows and Linux were added, along with blocking CI audits.
  5. The container base image and GitHub Actions are now pinned, publishing permissions were narrowed, and active Linux and Windows CI was restored.
  6. The governed Windows release gate now runs in a clean Python 3.11 environment before its isolated smoke and build stages.
  7. Invalid release inputs now fail closed, while the owner-controlled boundary for signing, tagging, publishing and deployment stays intact.
  8. Root agent governance and a canonical, side-effect-aware operations runbook were added for diagnosing BUS Core, Lighthouse and Agent Smith.
  9. Update-route evidence is now kept apart from product-event evidence, and the exact semantics of acknowledgement, retry, local state and delivery proof are documented.
  10. Documentation on update checks, manual signed staging, next-start handoff, auth, write gates, AppData, the release mirror and build side effects was aligned with what is actually implemented.
  11. Unresolved drift in analytics, privacy, generated compliance and code comments is recorded in the changelog, so deferred work stays visible and is not mistaken for shipped behavior.
  12. Known limits: the telemetry signal-authority conflict, hardcoded non-authoritative UI and report status, the silent preference-save failure on first run, packaged privacy and test drift, the generated tgc-ops compliance projection, and the future update, restart and Docker decisions remain unresolved; the full list is in CHANGELOG.md under 1.4.2.
  13. The owner chose public version 1.4.2 and reset the internal revision to 1.4.2.0; this preparation does not build or sign artifacts, create commits or tags, publish releases or manifests, or deploy anything.

New programs