Most industrial software takes 6 to 18 months to deploy. We don't run that kind of project. Here's how a Vigora deployment actually works.
A typical Vigora deployment for a one-to-five-section site moves through six stages. Three involve you. Three are on us. The whole thing typically takes one to two days for the smaller deployments, slightly longer for sites with more machines.
You fill out an inquiry form on this site. Company name, contact, basic information about your machines and process, NDA agreement. Five to ten minutes of your time.
Done by You
Our team reviews your inquiry within one to two business days. We confirm whether Vigora is a fit for your operation. If yes, we send you a personalised secure link to capture deployment-relevant details.
Done by Us
The secure link takes you to a structured form. You provide PLC details, network topology, machine inventory, signal lists if available, recipe targets, operator contacts, site contact. Roughly 30 to 60 minutes of your time, often spread across one or two sessions while you check details with your team.
Done by You
Our team prepares your deployment package internally. We select or build the right machine profiles, generate your site configuration, prepare signal mapping, set up recipe targets, generate your license key, pre-provision your admin credentials, and bundle everything into a single deployable artifact. This typically takes one to two business days.
Done by Us
You receive a secure download link. Your IT downloads the package, runs one command on your factory server, and Vigora boots up fully provisioned. Approximately 15 to 30 minutes of your IT person's time.
Done by You
Operators receive their pre-issued credentials and log in. We schedule a brief walkthrough call (30 to 60 minutes) with your operations team to make sure everyone is comfortable. Vigora is now observing your factory floor in real time .
Done by Both
Most enterprise MES deployments require your team to do things they shouldn't have to. Vigora's gated white-glove model removes those:
You don't:
We do all of those internally as part of Step 4. Your IT runs one command. Your operators log in with credentials we've issued. Everything else is on us.
Some industrial software vendors offer 'self-service deployment' — download our installer, run it, configure it yourself. We considered that path and rejected it.
Self-service deployment shifts hard work onto your team. Industrial integration has dozens of specifics — PLC make and model, network topology, data block layouts, signal offsets, recipe specifics — that are quick for our team to handle and slow for yours. Our approach: we collect what we need from you in a structured form, then we do the integration work, then you get a one-click deployment.
This costs us more per customer. It's worth it because it gets you live in days instead of months, and because the alternative (your team writing PLC integration scripts) is exactly the kind of work that derails enterprise software projects.
After Vigora is live, your team has a clearly bounded self-service envelope. You don't come back to us for the everyday stuff. You do come back to us for the bigger changes.
You can, without us:
You come back to us for:
The customer self-service envelope grows over time. As we mature features and as your team gets comfortable, more of what's currently 'come back to us' moves to 'you can, without us.' The boundary is deliberate, not technical — it's there to keep operationally consequential changes auditable and supportable.
The fastest path is to start the inquiry. We'll review and respond within one to two business days. There's no obligation; the inquiry is just the first conversation.