Many clients say: “Ok, but after we receive the software, what do we do with it?” An IT project does not end at delivery — it ends when it runs stably, day after day. Here is what we are asked most after implementation and how we work at IOTNetWEB.
Who handles hosting and maintenance?
We do — if you want us to.
We offer secure hosting in Romania for custom applications, not only presentation sites:
- monitored servers, tracked uptime;
- automated backups, stored separately;
- regular security patches;
- support when something breaks.
Your data — consumption, production, customers — deserves infrastructure you know. Not an anonymous server with no SLA and nobody to call at 2 a.m.
You can use your own infrastructure; we recommend ours when we built the software — we know how it must run.
What when bugs appear or you need new features?
Normal — that is why technical support exists.
Bugs: you report (email, phone, ticket) → diagnosis → fix → confirmation.
New features: discuss → estimate → build → test → launch without breaking what works.
Custom software is alive. The business evolves, the software with it. Not “delivered and forgotten” — a partnership, if you want one.
Most clients stay with the same team that built the platform — not a call centre without context.
How are applications protected against attacks?
Security is in the design, not an add-on.
- role-based authentication;
- HTTPS/SSL;
- framework and server updates;
- access logs;
- backup and recovery plan;
- monitoring for abnormal behaviour.
For automation and IoT, industrial panels are constantly scanned by bots. We protect every platform seriously, regardless of size.
What does go-live include?
Usually: data migration (if needed), user accounts, short training, minimal documentation, stabilisation period with priority response. We clarify the checklist in the contract so there is no “we thought that was included”.
Checklist after delivery
- Do we know whom to call and how fast they respond?
- Where are backups and when was restore last tested?
- Who has admin access and how is it reviewed quarterly?
- Do we have a plan if the site drops during a campaign or billing season?
- How do we request a new feature without chaos?
Minimal documentation — accounts, backup procedure, support contact — is not luxury. It is what saves the weekend when a key person leaves the company.
Training — how much is enough?
Usually 1–2 live sessions plus a short written guide (PDF or internal page). We do not teach programming; we teach operators to use the platform for their job. The rest is our maintenance work.
Migrating from the old system — without drama
Many projects do not start from zero: Excel, legacy software, paper. We plan imports, parallel periods, rollback if something fails. Go-live does not have to be an all-nighter — it can be a morning with the team ready and data verified.
SLA and realistic expectations
“Response in 15 minutes” sounds good in a quote, but prioritisation matters: presentation site down vs billing portal stopped. We agree urgency levels together, so you know what you get at night and on weekends.
How IOTNetWEB helps
From presentation sites and online stores to IoT platforms — we build, host, maintain. One partner from idea to years of operation.
What the maintenance contract should cover
Included hours for small changes, incident response time, what counts as a “new feature” vs a bug, backup/restore procedure, direct contact (not only a form). Sounds boring until the site drops on Black Friday or on utility billing day — then you want to know exactly what you bought.
Knowledge transfer
If you ever change partners, you must leave with data, access, documentation. We deliver that as a normal part of the project, not a favour. Custom software without transfer is dependency, not partnership.
Versioning and staging
Serious projects use a test environment: you try new features before customers see them. We set that up as standard for apps that handle money or meter data — not as a luxury add-on.
One takeaway
Launch day is day one of operations, not graduation. Plan who runs the platform, who you call, and where backups live before you celebrate go-live.
Want to start your next project on solid ground? Contact the team — we discuss your needs, no pressure.
Posted on Aug 01, 2026.