Low-code for Defense Manufacturing: What to Choose

Rapidly automating defense manufacturing on a low-code platform is entirely possible, but the platform itself knows nothing about acceptance certificates or export licenses. Therefore, do not compare platforms—compare what is already built on them and what you will have to build yourself. Below is a list of commonly considered platforms and seven selection criteria.

Platform and Application: Two Different Things

A low-code platform provides a builder: fields, forms, processes, permissions, and reports. Defense manufacturing asks different questions: which contract does this product belong to, who signed the acceptance certificate, which license covers the export, and which batches were used to assemble this serial number?

These answers do not come out of the box with the platform. They must be modeled: registries of contracts, certificates, licenses, and batches, the rules linking them, and pre-shipment checks.

Therefore, a project offers two paths. You can build this on a blank platform yourself, or you can take a ready-made application built on the platform and configure it to your needs. The second path represents true "rapid automation": the core registries already exist, and your work begins with validating your own contract.

Platforms Commonly Considered

These are general-purpose platforms: none of them is a manufacturing system on its own. This list is neither a ranking nor a recommendation—each platform has its own strengths. Evaluate them against the criteria below.

Creatio: A no-code platform for process automation and CRM. Syntech Manufacturing is built on it.

Microsoft Power Platform: A suite of low-code tools within the Microsoft ecosystem.
OutSystems: A low-code application development platform.
Mendix: A low-code application development platform.
Appian: A low-code process automation platform.

In addition to these platforms, there are two other paths: an MES with a built-in configurator and ready-made manufacturing applications on a low-code platform. Syntech Manufacturing belongs specifically to the second group.

Seven Selection Criteria for Defense Manufacturing

Where the system runs. Within your perimeter (on-prem or private cloud) or are external services required? For a manufacturing environment, it is best if external services are not needed.
What already exists for the defense context. State defense contracts and delivery schedules, acceptance certificates, batch and serial number traceability, export control, qualifications, and audit packages for license verification. Either this is already built, or you will have to build it.
Who modifies the system after launch. Your administrators or an external contractor? And do your customizations survive platform updates? In Syntech Manufacturing, localization and core configurations are delivered within a package, while your customizations live in a separate dedicated package, so reinstallation never overwrites translations.
Access permissions. Record- and column-level permissions, audit logs, SSO, two-factor authentication, and isolation by contracts and projects. For sensitive data (rates, military registration, licenses, certificates), permissions must be configured during the implementation project.
The two-person rule. Can the creator of a request approve it themselves? Can the person who submitted an acceptance certificate approve it single-handedly? This must be enforced by system rules, not verbal agreements.
An honest list of limitations. Ask the vendor what their system cannot do. If there is no clear answer, you will find out about limitations during final acceptance rather than before purchase.
What vendor certifications actually cover. A platform vendor's certificate does not make your deployment compliant: it is merely evidence used by the system owner during evaluation. Security authorization under Cabinet Resolution No. 712 must be obtained by you. For on-prem installations, the vendor's cloud certifications do not apply to you.

What a Quick Start Looks Like

A reliable way to test any platform or ready-made application: one contract and one serial number, not the entire factory at once.

Take your state contract and a single serial number.
Trace them from the delivery schedule to the acceptance certificate, license check, and proof package.
See what the system does not cover: an honest vendor will point this out themselves.
Only then expand the system to other contracts and production areas.

This way, you see actual operation rather than a sales pitch, and you know what customizations are required before committing to a purchase.

What We Do in Syntech Manufacturing, and What We Don't

Syntech Manufacturing is an MES/MRP solution built on the Creatio platform: 61 sections, three languages, deployed within your perimeter. A single data environment for design bureaus, assembly lines, and finance: bills of materials, work orders, inventory, serial numbers, and contract documentation.

What is included:

15 functional roles—from planner and QC inspector to military representative and export control officer—each with a dedicated workplace;
On-premise or private cloud deployment, with no external services required for the manufacturing perimeter;
Full mapping against the requirements matrix of Ukrainian defense manufacturing: out of 29 business requirements, 27 are covered completely, 2 are not. An additional 8 platform capabilities (record-level permissions, audit logs, backup, isolated deployment) are provided by Creatio and are not included in those 29.

What is not included:

State secrets clearance registry;
Integration with DOT-Chain Defence and other defense marketplaces;
Built-in qualified electronic signature (QES) provider: a third-party qualified provider is required;
Automated end-user screening: this is handled manually;
Default hard blocking for most validation checks: prohibited parties and countries are always blocked, but license, certificate, acceptance, qualification, equipment, and WIP limit checks issue warnings by default until an administrator enables hard blocking;
Accounting system replacement: general accounting remains external.

And most importantly, to state it clearly: the product holds no official security certifications. We designed it around the operational requirements of Ukrainian defense manufacturing, which is not the same as being certified against them.

Common Mistakes

Comparing platforms rather than outcomes on your specific contract. A toolset cannot provide answers to a military representative; only the system built on it can.
Building what already exists from scratch. Registries for contracts, acceptance certificates, and licenses are required by every defense manufacturer, and there is no reason to model them again.
Overlooking access permissions. Military records, rates, and acceptance documents should never be visible to everyone.
Mistaking a vendor's certificate for certification of your own system. It certifies the platform vendor's internal processes, not the compliance of your specific deployment.
Launching across the entire plant at once. It is far safer to start with a single contract and a single serial number.

Frequently Asked Questions

Is a low-code platform enough to automate defense manufacturing? The platform alone is not enough: it provides the toolset, but contracts, acceptance certificates, traceability, and export controls must either come with a pre-built application or be engineered from scratch.

Can the system be deployed within our own perimeter? With Syntech Manufacturing, yes: on-premise or private cloud according to your requirements; no external services are needed for the manufacturing perimeter.

Does the product have official certification? No. It is built to meet the operational requirements of Ukrainian defense manufacturing, but that is not equivalent to being certified. The compliance of your deployed system is evaluated by its owner.

Does Syntech Manufacturing replace an accounting system? No. The module tracks advances, sets them off against shipments, and tracks order costs, but it does not replace financial accounting software.

What does Syntech Manufacturing not do? It lacks a state secrets clearance registry and integration with DOT-Chain Defence, and a third-party provider is required for qualified electronic signatures. A complete list of limitations is available on the product page, and we openly demonstrate the two matrix requirements that the product does not cover during our demo.

Book a Demo

Bring your state defense contract and a serial number. During the demo, we will trace them from the delivery schedule to the acceptance certificate, license verification, and proof package, and we will highlight the two matrix requirements the product does not cover.

Book a demo and learn more about the system