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.