01 / Inventory
Record versions and dependencies.
Infrastructure
01Infrastructure02Monitoring03Recovery
KG-NET / Maintenance & support
Maintenance with a traceable routine.
Planning, design and technology are considered together. Scope and price follow your actual requirements.
01Infrastructure02Monitoring03Recovery
Maintenance & support
How it comes together.
Three perspectives on your project. Scroll through the process or select a step.
02 / Maintenance
Run backups and agreed updates.
Monitoring03 / Verification
Check forms, store and login journeys.
RecoveryWORKING TOGETHER
Clearly agreed. Clearly delivered.
A defined scope
Before work begins, we agree goals, content, responsibilities and integrations. You know what is included and what needs a separate plan.
Reviewable milestones
Structure, design and function are reviewed in clear stages. Decisions follow your requirements and feedback.
A clear handover
The agreed scope defines access, guidance and an understandable operation and maintenance plan. Ongoing support is agreed explicitly.
Website maintenance: Predictable website care with documented changes and clear ownership.
What we build with you
Updates often affect more than a version number. We consider dependencies, backups and important user journeys. An agreed maintenance window and rollback plan help keep changes controlled.
- Update inventory
- Pre-change backups
- Functional checks
- Maintenance log
Maintenance combines updates with functional checks and recovery options. We inventory relevant components and agree a maintenance window. Backups are useful only when restoration is organized. Changes remain traceable. External licences and abandoned extensions receive separate review so an update does not silently disrupt essential functions or agreed integrations.
How the project takes shape
Inventory
Record versions and dependencies.
Maintenance
Run backups and agreed updates.
Verification
Check forms, store and login journeys.
What makes working with KG-NET clear
We discuss how your business actually works before specifying individual features. Dependencies, responsibilities and the agreed scope are documented. Decisions are discussed using actual pages, tasks or data flows. Questions, materials and approvals are coordinated with an accountable contact. During handover we clarify what your team can maintain and which technical work requires a separate service. You can see what was agreed and where an additional decision is needed.
20 / QUESTIONS & ANSWERS
Decide with clarity.
Which infrastructure is used?
Provider and package depend on requirements. Specific server facts come from verified information or connected APIs.
How are backups checked?
Backup status alone is not enough. Scope, retention and restore tests need to be defined and documented.
Are automatic updates always safe?
No. Changes may affect dependencies. Critical updates need a backup, testing and a rollback path.
What does a security check show?
Only signals actually checked, such as headers, versions or integrity data. A quick scan does not prove complete absence of malware.
Can I use cPanel?
A connected and authorised hosting integration can provide a short-lived login link. Access remains limited by the hosting account.
How are DNS and domains managed?
Ownership, registrar, nameservers and responsibilities are documented. Changes are reviewed for website and email effects.
What do SPF, DKIM and DMARC mean?
They support sender authentication. Correct records are useful signals but do not guarantee inbox delivery.
What happens during an incident?
A detected event receives an owner and status. Actions, review and resolution are documented; risky intervention requires approval.
How does the project start?
We clarify the audience, existing systems, responsible people and intended outcome, then agree the scope.
What determines the price?
Scope, integrations, content, licences and support are considered separately. You receive an individual offer before delivery starts.
When is the schedule agreed?
After discovery and prioritisation we agree milestones. Approvals, access and external dependencies influence dates.
Who supplies content and access?
We agree which text, images and data you provide. Access should use roles, invitations or limited tokens wherever possible.
Can existing systems keep running?
Yes, subject to a technical review. We plan changes, backups and rollback paths to keep the transition controlled.
How are changes agreed?
Questions are collected in the project. Extensions get a defined scope and approval before additional implementation.
How is acceptance handled?
We agree concrete test cases and responsible people. Open issues are documented and release follows the agreed approval.
Is a handover session included?
Handover can include training, documentation and defined access rights. The scope and format are specified in the offer.
What happens after launch?
Support, updates and response times are agreed separately, making internal and KG-NET responsibilities clear.
How is personal data handled?
We limit access and review data flows, retention and processor arrangements. Legal approval remains with the controller and their advisers.
Can you work across borders?
We work with businesses in Austria, Germany, Switzerland and Serbia. Language, responsibilities and actual market needs are agreed together.
How are outcomes assessed?
We agree verifiable goals and identify the data source. Without connected measurement there are no invented metrics or guaranteed outcomes.
Plan the connected services together
Depending on your project, we align this service with related areas. Content, technology and responsibilities should fit together. Discuss the interfaces and actual scope you need with us:
THE NEXT STEP
Your idea. A clear plan.
Tell us what you want to change. We will clarify goals, scope and the right approach, with an individual proposal.
KG-NET
Ilija Benjak
Völkermarkter Straße 280
9020 Klagenfurt am Wörthersee
Austria