AUTONEST VCReliability · Trust

Even when our server has a bad day, your calculation doesn't stop

2026-09-21 · 4 min read

Tools that run in the cloud stop the moment their server stumbles — the screen goes blank, a save fails, or you simply can't log in. AUTONEST VC is built differently. Both the calculation and the drawing run on your own PC. The server checks exactly one thing: your license. So if your connection drops, or something goes wrong on our end, work keeps going for up to 7 days after your last successful check-in.

Runs entirely on this PC Calculation engine thickness · strength Drawing logic drawing file (DXF) Spec databases plate · thickness · flange now & then Server license check only

1. Calculation was never meant to live on a server

The engine that sizes thickness and checks strength, the logic that draws the vessel, and the databases of plate, thickness and flange specifications — all of it sits as files on your own PC. Press [Calculate] in AUTONEST VC and the calculation runs on your PC and the drawing file is created right there. A shop can edit its own plate list precisely because that data is local.

The server plays no part anywhere in that flow. All it does is confirm that this license is valid.

2. You still need the internet — just not every time

To be upfront: internet is not entirely optional. You need it to install, and periodically after that to reconfirm your license is active. The difference is that this check doesn't have to happen every time you calculate — once every 7 days is enough.

From your last successful check-in, you have 7 days during which calculation and drawing continue normally whether your connection drops or our server runs into trouble. A day or two of intermittent internet on a shop floor won't stop the work.

3. The same applies when the trouble is on our end

There was a time our authentication server was far less stable than it is now. It went down multiple times a day, and every time it did, it was obvious: if the server dies, every customer's work stops with it. This 7-day grace period was built after that lesson. If our own mistake or an outage knocks the server out for a few hours or a few days, the screen you're designing on that day should not go dark because of it.

We now run on a dedicated server in a Seoul region and it's far more stable. Even so, we designed around the assumption that a server can stumble someday, and that assumption is still what this grace period protects against.

4. After 7 days, you do need to reconnect once

We're not going to hide the boundary here. If 7 full days pass with no successful connection to the server, the next launch asks you to connect to the internet, and calculation is held until re-authentication succeeds. This is not a design for unlimited offline use.

The reason for the line is simple. A license ultimately confirms your subscription period and payment status, and with no check at all that stops being a grace period and just becomes no authentication. Seven days is the balance point: absorb a short outage or a trip away from the internet, but eventually reconnect once.


What this means day to day

Most days you'll never notice any of this — with a normal connection it just checks quietly and moves on. The one day this becomes visible is exactly the day your internet or our server misbehaves. That your calculation doesn't stop on that day is the whole point of this design.

The same principle applies when we ship a new version of the program itself.

An update that never ruins the work in front of you →