Clearer service boundaries
Separate website, email and server hosting from the business connection that reaches them, so requirements and responsibilities are easier to discuss.
Plan website, email and server hosting separately from business internet connectivity, then coordinate the dependencies where your people, locations and hosted services need to work together.
A considered discussion begins with the environment you have today.
Internet hosting, with clear scope and ownership.
The Southbank intake asks for workplace locations, remote-working requirements and the systems managed internally. Separate the hosting needs for websites, email or servers from the business internet and multi-site network requirements that support access to them.
Southbank sits on the southern side of the Yarra River Birrarung, where the riverside promenade includes restaurants, hotels and city views.
The Melbourne Arts Precinct in Southbank brings together the National Gallery of Victoria, Hamer Hall, galleries, theatres, studios and arts education institutions.
vCloud's service catalogue identifies Hosted Exchange / Web Hosting and hosting services as a distinct area. Discuss the website, business email, hosted workloads and server requirements that need a suitable hosting environment, access controls and clear ownership.
Tell us what you need. We’ll help you understand the options and decide what comes next.
Use the enquiry form to tell us about your requirements.
Share the issue you’re facing, what you want to improve and any systems already in place.
We discuss your current setup, the people it needs to support and any practical requirements.
We explain suitable options and discuss the scope so you can decide how to proceed.
Hosting support concerns the website, email or server environment: access, domains, workloads, administrative ownership and the systems that depend on them. Connectivity support concerns the business network, locations, routing and the path users take to reach those services. An issue can cross both areas, so the support scope should explain who owns each layer and how escalation works.
Bring current diagrams or provider details where available, along with domains, hosted workloads, sites, users, critical applications and the business impact of an outage. This makes it possible to distinguish a hosting fault from a local network or internet-access problem instead of sending the issue between providers without a shared record.
Remote assistance, premises access, hands-on equipment work, local delivery, response arrangements and service levels are subject to confirmation in the proposal. This sandbox profile does not promise local availability or a particular support commitment.
Remote support for Internet hosting helps your Southbank team work through service questions and issues without needing an office visit.
You can access Level 1–4 support engineers for help with your Internet hosting requirements, from initial troubleshooting through to more involved technical investigation.
If the work needs a hands-on response, the remote engineer can escalate it to an on-site engineer for a visit to your office in Southbank.
Appointment, scope and access can be confirmed when you contact us.


We can visit your office in Southbank when Internet hosting work needs hands-on attention. Our engineers are in and around the area daily.
Same-day visits can be booked for urgent support issues, with next-day support for issues that can wait. We confirm the appointment, scope and access arrangements when you contact us.
Whether the hand-off starts remotely or on site, the discussion can stay focused on the work in front of your team.
Appointment, scope and access can be confirmed when you contact us.
Visits focus on your Internet hosting requirements. The work, responsibilities and ongoing support are agreed with your team.
This service has two deliberately separate workstreams: hosting for online services and business connectivity for access between people, locations and those services. The final scope should state which workstream is included and how they depend on one another.

Define the hosting requirements for a business website.
Review the website's purpose, domains, traffic patterns, content ownership, deployment responsibilities and operational dependencies so the proposed hosting environment is based on the actual site rather than an assumed package.Discuss this requirement
Plan hosted email around people, domains and access needs.
Discuss mailboxes, shared addresses, domain requirements, user access, security considerations and continuity expectations. Hosted email is an email service scope; it is not the same thing as providing the internet connection used to reach it.Discuss this requirement
Map server workloads and their hosting requirements.
Identify applications, data, access patterns, operating responsibilities and dependencies for hosted or virtual server workloads. Keep workload hosting decisions distinct from the office network and internet access that connect users to them.Discuss this requirement
Translate operational needs into a business connectivity brief.
Document locations, users, working patterns, cloud and hosted-service dependencies, voice or collaboration traffic and the consequences of an interruption before selecting a connectivity approach. Specific service options require assessment and confirmation.Discuss this requirement
Plan how offices and remote users connect to shared services.
For multiple locations, map sites, routing relationships, private access needs, internet egress, cloud workloads and administrative boundaries. The source catalogue's Multi-Site Cloud Network is a network-planning reference, not a promise of a particular topology.Discuss this requirement
Make the hand-offs between hosted services and networks visible.
Trace which users, sites and systems rely on each hosted service, where names and access are managed, and what needs attention when connectivity changes. Use the resulting scope to separate provider responsibilities and reduce avoidable hand-balling.Discuss this requirementBring the detail that affects your people, systems and decisions into one practical discussion.
Separate website, email and server hosting from the business connection that reaches them, so requirements and responsibilities are easier to discuss.
A documented view of users, locations, hosted systems and traffic dependencies can expose practical constraints before a connectivity change is treated as a simple order.
Mapping sites, access paths and shared workloads gives decision-makers a concrete basis for discussing remote work, inter-office access and future locations.
Hosting and connectivity can be planned together without pretending they are interchangeable, helping clarify escalation, documentation and the next decision.
Different working environments bring different systems, rhythms and priorities into focus.

Bookings, point-of-sale systems and office tasks place different demands on a venue's technology. Discuss staff networks, connectivity and support ownership while confirming the role of hospitality-platform and payment providers.
Read perspective
Policy records, client communication and specialist platforms should be considered as one working environment. Discuss access and recovery priorities while confirming professional obligations and keeping insurance-platform responsibilities separate from general IT support.
Read perspective
Online orders, fulfilment and customer communication span several systems. Consider staff access, integrations and business continuity while clearly distinguishing workplace support from the online store and marketplace platforms themselves.
Read perspectiveFeedback from our clients.
Yarra Accounting Group have been with vCloud for over 2 years. In that time we have embraced the true power of cloud computing and created a paperless, cloud accountancy firm. As our time is spent working from client sites, the traditional office was unnecessary. The office simply housed our technology… but no more!

Website, hosted email and server workloads are resources delivered from a hosting environment; business internet connectivity is the access layer that lets offices, remote users and systems reach required destinations. A sound brief names both layers, their dependencies and the boundary between them.
For a single office or multiple sites, start with domains, hosted workloads, users, locations, applications, traffic patterns and any access that must remain available during an interruption. The Multi-Site Cloud Network source supports treating locations and network functions as a deliberate design problem, while the hosting catalogue supports a separate discussion of Hosted Exchange / Web Hosting and internet services.
The proposed architecture, service demarcation, security responsibilities and any resilience approach must be confirmed against the organisation's current environment. This profile does not establish a particular carrier, connection type, performance level or topology.
Straightforward answers to help you understand your options.
No. Hosting covers resources such as a website, hosted email or a server environment. Business internet connectivity is the access service people and locations use to reach those resources and other online systems, so the two requirements should be scoped separately.
Yes, they can be discussed in one coordinated scope while remaining separate workstreams. Hosting should cover domains, mailboxes, workloads and administration, while connectivity should cover users, sites, access paths and dependencies; the agreed scope should state what is included in each area.
Bring details of your domains, website and email arrangements, hosted or on-premises servers, users, sites, current providers, key applications, remote-working needs and any links between locations. Existing diagrams, account details and recent issues are useful, but you do not need to diagnose the cause first.
No. Multi-site connectivity plans how locations and users reach shared systems; it does not itself provide the website, email or server workload. The two areas can depend on each other, so both should be documented and scoped rather than treated as interchangeable.
Premises access, hands-on equipment work, local delivery, response arrangements and on-site support need to be confirmed for the actual address and proposed scope. This service information does not guarantee local availability or a particular support commitment.
First identify whether the hosted service, local equipment, business network or internet access is affected. Record the critical services, responsible parties, contact paths and checks needed for each layer; any continuity or recovery work would be agreed as a separate scope.
Tell us which websites, email services, server workloads, users and locations matter to your organisation. We can then separate the hosting and connectivity requirements, map their dependencies and confirm a practical scope for discussion.