Original system architectures across healthcare, assistive technology, logistics, mobility, construction and travel.
The public layer shows what each system is designed to do. The architecture that makes it work remains protected.
A DYNAMIC IP PORTFOLIO
Some architectures are developed directly by Archestral Studio. Others may be sold, licensed or transferred to organisations capable of taking them into execution.
A strong architecture should not remain dormant simply because one studio cannot build everything it designs.
The objective is not to retain every project. It is to give good projects a realistic path to being built.Healthcare · Clinical Decision Support
Complete System ArchitectureA complete, implementation-ready architecture for secure medical decision support.
Doctor Deck is a family of purpose-built medical systems designed to give clinicians a fast, controlled and clinically useful second layer of memory and decision support. It combines dedicated hardware, local computing, curated medical knowledge, probabilistic clinical support and a deliberately constrained use of generative AI.
The objective is simple: reduce cognitive load without transferring clinical authority away from the physician.
Generative AI is confined to the functions for which it is useful: natural-language interaction, medical interviewing, information organisation and document generation. Clinical support is produced separately through a controlled probabilistic system operating on curated medical knowledge.
Security is treated as a system property spanning hardware, software, data and deployment rather than as an additional layer applied at the end.
ARCHITECTURE SCOPE
What is shown publicly is the boundary and purpose of the architecture — not the internal architecture itself.
Surgical Training · Physical Simulation · Virtual Reality
Architecture in DevelopmentA hybrid surgical training system combining a modular physical patient with virtual reality, sensing and procedural assessment.
The system is built around a simple principle: reproduce physically only what the surgeon actually needs to feel and manipulate.
The synthetic patient provides physical geometry, resistance, cutting, suturing and manipulation. Replaceable tissue and organ modules are designed as low-cost consumables, so damage can be part of training rather than something the user must avoid.
Unreal Engine 5 provides the surrounding clinical reality and allows the system to reproduce changing operative conditions, including rare events and complications, while the surgeon continues to work on the physical patient.
The system also supports instructor supervision and post-procedure assessment, making each session measurable, reviewable and repeatable.
Real where physical interaction matters. Simulated where digital reconstruction is sufficient. Replaceable where damage is part of learning.
ARCHITECTURE SCOPE
Materials, sensing methods, measurement architecture, haptic mechanisms and other implementation details remain protected.
Assistive Technology · Independent Mobility
Complete System ArchitectureA wearable assistive mobility system designed for blind and low-vision users.
FeelAround combines smart glasses, body-worn sensing, haptic feedback and audio guidance to create continuous awareness of the user’s immediate surroundings and support safer, more independent movement.
The architecture is local-first. Core safety functions can operate autonomously without a smartphone or internet connection. When available, the smartphone extends local processing for more complex perception, navigation and contextual functions.
The project is not built around a single device or a single recognition feature. It is a coordinated assistive system spanning wearable hardware, distributed sensing, local processing, accessibility-first interaction and operational ergonomics.
Local-first. No cloud dependency. Core safety remains available even without the phone.
ARCHITECTURE SCOPE
Only the system purpose, user boundary and selected capabilities are described publicly. Sensor topology, internal safety logic, processing architecture and implementation mechanisms remain protected.
Road Freight · Workforce Architecture · Continental Operations
Complete System ArchitectureA continental workforce architecture for reorganising how professional drivers are supplied, rotated and deployed across European road freight.
Instead of treating the driver shortage as a recruitment problem, the system redesigns the relationship between drivers, vehicles, working time, rest, location and freight.
It combines a pan-European verified driver marketplace, an emergency replacement network and a continuous shift architecture designed to maintain operational continuity across borders.
The architecture is designed to remain economically viable at low market penetration rather than depending on mass adoption. Greater scale improves network efficiency, but it is not required to make the system work.
Driving.By.24 builds on earlier real-world validation in European road transport through Japojade.pl.
ARCHITECTURE SCOPE
The public layer describes the system boundary, not the deployment topology, matching logic, operating thresholds or internal commercial mechanisms.
Road Freight · Logistics Infrastructure · Continental Coordination
Complete System ArchitectureA continental freight coordination architecture designed to move European road logistics from manual market transactions toward automated, system-level flow.
Instead of beginning after a load is posted to a freight marketplace, Syncargo begins at the point where the load originates: the production and ERP layer.
The system brings load data, transport capacity, cross-border compliance, economics, risk and execution into one coordinated operating layer without requiring manufacturers or carriers to replace the systems they already use.
Syncargo is designed as standalone infrastructure. It can integrate with other systems, including Driving.By.24 as an optional operational extension, but does not depend on them for its core function.
The commercial architecture is designed to become economically viable at low market penetration; greater scale increases network density and efficiency, but is not required to make the architecture work.
ARCHITECTURE SCOPE
Internal data models, decision logic, orchestration mechanisms, scoring, compliance logic and security architecture remain protected.
Travel · Narrative Experience · Cultural Infrastructure
Complete System ArchitectureA complete system architecture for a new form of guided travel.
Audiotravel transforms the traditional audio guide — often a dedicated playback device or a manual list of numbered recordings — into a continuous guided experience available directly on a traveller’s phone.
The central idea is simple: a real guide in your pocket. The traveller is accompanied through a place by natural narration designed around the experience of actually being there.
The system is built around curated human storytelling and can support experienced local guides, thematic routes and selected Celebrity Routes. It also extends into VR Travel and a separately operated, non-commercial VR Heart layer.
Audiotravel is designed as scalable narrative and cultural infrastructure for cities, cultural institutions and travel environments — not as an open content marketplace.
ARCHITECTURE SCOPE
The underlying route logic, spatial activation model, narrative-control architecture and implementation logic remain protected.
Construction Intelligence · Estimation · Planning
Complete System ArchitectureA construction intelligence architecture designed around the moment when a scope of work becomes a commercial and operational decision.
For small construction and trade firms, Estima App replaces fragmented notes, spreadsheets and manual estimating with a field-ready environment for preparing structured professional offers and the planning information needed to decide whether, when and on what terms a job can be delivered.
Estima Pro extends the same architectural foundation to larger contractors and developers, supporting project-level estimation and planning where the scale and complexity of documentation make traditional manual workflows slow and expensive.
The two operational layers are designed for different users, but belong to one construction-intelligence system. The objective is not to replace every tool used by a construction company, but to make estimation and planning structured, repeatable and data-backed from the beginning.
ARCHITECTURE SCOPE
The calculation logic, backend behaviour, data relationships, commercial workflow and internal system architecture remain protected.
Premium Mobility · Passenger Transport · Hospitality
Complete System ArchitectureA premium mobility system designed to provide the same standard of safety, elegance, comfort and service quality across multiple European markets.
Rather than operating as a mass-market ride-hailing platform, the architecture is built exclusively around premium mobility. Vehicles, drivers, customer experience and operational standards are treated as one consistent service environment.
The objective is simple: a passenger using Lion’s Transfer in different cities should receive the same predictable premium experience without having to evaluate a different local provider each time.
The system is designed for airport transfers, business travel and premium urban mobility, with the ability to extend the same service standard across countries and transport formats.
Its value comes from standardisation at system level: the service is designed to remain recognisably premium wherever it operates, rather than becoming a collection of locally different transport services.
ARCHITECTURE SCOPE
Market-entry architecture, fleet economics, commercial structures, partner models, operational scaling logic and internal system mechanisms remain protected.
Industrialised Construction · Modular Housing · Factory Architecture
Complete System ArchitectureAn industrial system for the factory production of high-performance modular buildings.
The architecture is built around a standardised module as the fundamental production unit. Complete modules are manufactured through a repeatable factory process and can then be combined into different residential and commercial configurations.
Aurora was designed as a production system rather than as a collection of individual house designs. The architecture extends beyond the building itself into the factory layout, production flow, quality control, logistics and the organisation required to manufacture complete modules consistently at scale.
The modules are designed to a very high thermal-performance standard, combining industrial repeatability with the quality expected from premium permanent buildings.
The wider architecture can also incorporate circular material streams, including the reuse of material recovered from retired wind-turbine blades in selected building components.
ARCHITECTURE SCOPE
Detailed module construction, material assemblies, production methods, component architecture, process sequencing and other execution logic remain protected.
PUBLIC BOUNDARY
Only selected system purposes, boundaries and capabilities are presented publicly. The underlying architectures may include proprietary operational logic, hardware and software structures, economic models, decision systems, production methods, market-entry mechanisms, data relationships and other implementation-critical elements.
The level of public disclosure differs by project because the protected value is not always located in the same layer.
In some systems, the technology is conventional and the architecture itself is the invention.