Built for operational responsibility, not just software functionality
ProviCost is an operational platform built specifically for fresh produce processors. Its architecture is designed around a simple principle: important operational information needs a clear owner, a reliable history and a controlled path from the person recording an event to the business evidence management relies upon.
Business language first. Architectural substance underneath.
ProviCost separates operational responsibilities so the evidence created by Purchasing, Receiving, Inventory, StockTake and future capabilities can remain attributable and authoritative.
The objective is not technical complexity. It is dependable operational truth.
A serious platform underneath
The current ProviCost platform is built on .NET 8, ASP.NET Core, SQL Server and Entity Framework Core. Secure APIs and shared contracts connect application responsibilities, while background processing and governed database migrations support work that must continue beyond a single screen interaction.
The solution separates Domain, Application, Infrastructure, API, Contracts, shared components and client responsibilities. That separation helps keep business rules, persistence and operator interfaces from becoming one indistinguishable layer.
Platform foundation
.NET 8 and ASP.NET Core
Application and API foundation.
SQL Server and Entity Framework Core
Transactional persistence and governed schema evolution.
APIs and shared application contracts
Defined boundaries between clients and application services.
Background workers
Support for responsibilities that should not depend on one operator interaction.
Access according to responsibility
ProviCost’s implemented security foundation includes authenticated user identity, ASP.NET Identity, role- and permission-based access control, protected application interfaces and password governance. Operator actions can therefore be associated with authenticated identities where the workflow records them.
ProviCost also applies a governed software dependency security lifecycle. Before the first production installation, the release must pass a mandatory SBOM-backed software supply-chain assurance gate. ProviCost does not claim security certification, penetration-tested assurance or other verification that has not actually been performed.
Security and release assurance
Foundation implemented. Identity, authentication, roles, permissions and protected API access form part of the current platform.
Production release assurance. No production installation may occur until the release has an immutable machine-readable SBOM linked to its authoritative Git commit and build/release identity, cryptographic integrity evidence and a recorded dependency-security assessment.
Deployed release identity. The installation must retain enough release identity to determine unambiguously which SBOM governs the deployed software.
Assurance boundaries. Where vulnerability intelligence is unavailable or incomplete, ProviCost records the result as UNKNOWN / UNAVAILABLE rather than treating missing information as successful verification.
A working example: Mobile StockTake
Mobile StockTake implements durable local evidence, queued delivery, acknowledgements, retry and replay handling, idempotent submissions, execution recovery and diagnostics.
Those mechanisms are evidence for this supported workflow. They are not a claim that every ProviCost capability works offline today.
Designed for the factory floor
Operational work does not wait for ideal connectivity. Where continuity is important to a mobile workflow, ProviCost is designed to preserve work locally, submit it safely when connectivity is available and let the server remain authoritative.
This approach is particularly important in receiving areas, fridges, storage locations and other parts of a working facility where a temporary network interruption should not automatically mean lost operational evidence.
Cloud-based without forgetting where the work happens
ProviCost is being developed as a cloud-based solution. Its ASP.NET Core, SQL Server and API architecture is compatible with hosted deployment, while relevant mobile workflows are being engineered so temporary connectivity interruptions do not automatically stop operational work.
The current architecture should not be confused with a claim that the final production cloud estate, high-availability design or disaster-recovery service is already complete. Those deployment responsibilities must be established and verified as the production platform matures.
Cloud direction
Platform direction: cloud-based access for authorised users without making the processor responsible for running the application infrastructure on site.
Operational principle: cloud access should not make a factory workflow unnecessarily fragile.
Traceability and governance
Evidence matters after the screen has changed.
Evidence that survives the screen
ProviCost includes a general audit capability and capability-specific operational records at different stages of maturity. Inventory transactions, StockTake observations, Receiving evidence, Purchasing evidence and governed decisions create histories that can remain available after the immediate operator interaction has ended.
This evidence-oriented architecture also supports ProviCost’s SQF-aware design. Traceability, authenticated decisions, procedure governance and retained evidence can support a processor’s food-safety responsibilities, but ProviCost does not claim SQF certification, guarantee compliance or replace the processor’s own food-safety programme.
For IT teams
ProviCost is intended to be understandable to the business and technically recognisable to the people responsible for introducing and supporting technology. The terms alongside describe mechanisms evidenced in the current platform or, where stated, the direction in which deployment is being developed.
.NET 8 / ASP.NET Core
SQL Server / Entity Framework Core
APIs and shared application contracts
Role- and permission-based access control
Server-authoritative operational records
Durable local evidence for supported mobile workflows
Queued and retryable synchronisation
Idempotent submission handling
Governed database migrations
Architecture compatible with cloud deployment
Technology experience behind the platform
ProviCost is developed by abacon IT, an established Cape Town technology consultancy with years of practical experience supporting South African businesses across business technology, infrastructure, cloud, networks, security and continuity.
That experience establishes the background of the company behind ProviCost. The platform’s own architecture, operational evidence and verified capabilities establish the credibility of the product itself.
Experience supports the company story. Evidence supports the product story.
This distinction matters. ProviCost’s technical claims are grounded in the platform being built, not inferred from abacon IT’s history.
A platform designed around operational truth
The architecture matters because the operation matters. ProviCost is being built so information can remain attributable, traceable and useful as it moves from operational activity to management understanding.
Talk to Us
Tell us a little about your operation, technology environment or what you would like to understand about ProviCost.