Interconnekt
Industry · Architecture

IT for Melbourne architecture practices.

Revit and ArchiCAD hosted on infrastructure that's been tuned for the workload, workstations specified against the software's actual demands, and the external collaboration security that doesn't break the way you share drawings.

Who we look after

4 Melbourne practices trust us.

Single-principal studios through to multi-discipline firms. Each engagement has at least one of BIM hosting, workstation lifecycle, or external collaboration security as the lead driver.

What's different in architecture

Four realities most generalist MSPs miss.

Architecture IT is workload-specific. Revit isn't Word, a designer's workstation isn't an admin laptop, and a model isn't a file share. The provider who treats it that way is the one who survives a deadline week.

Designers need workstations, not laptops.

Revit, ArchiCAD, Rhino, and V-Ray demand CPU, GPU, and RAM that a generic SOE laptop will not deliver. The difference between a $1,800 laptop and a $5,000 workstation is two extra billable hours per designer per week. Get the spec wrong and the practice pays for it in render queues.

Drawing storage isn't just file storage.

BIM models live in worksharing. Revit central files want low-latency access, not OneDrive sync. CAD libraries need versioning that survives a careless overwrite at 5pm on a deadline. We host central files on infrastructure that's been tuned for the workload, not generic file shares.

Project teams cross firm boundaries.

Consultants, engineers, and clients all need access to the model, but not to your whole environment. External sharing has to be granular, time-bounded, and auditable, or it becomes the next data breach. We design the sharing model first, the file structure second.

Deadlines kill the upgrade cycle.

There's never a good week to refresh hardware mid-project. The honest answer is a rolling 3 to 4 year replacement cadence with planned out-of-hours migrations, costed into the practice's annual budget. The provider who plans this gets the next decade of work.

Software stack we operate

Named, current, and operated in production.

Five software stacks architecture customers ask about by name. We've deployed each one, tuned the infrastructure for it, and operated it for at least one Melbourne practice.

Stack

Revit + BIM 360

Autodesk Revit and Autodesk Construction Cloud / BIM 360

What it needs

Worksharing on a low-latency Revit Server or BIM 360, workstations with adequate VRAM, and a backup strategy that handles 50-200GB central files without choking the network overnight.

How we deliver it

We host Revit central files on tuned infrastructure, baseline workstations against the Autodesk reference spec, and run backup windows that don't collide with the working day. Quarterly performance review against your largest live model.

Stack

ArchiCAD

Graphisoft ArchiCAD with BIMcloud

What it needs

BIMcloud server with predictable IOPS, library management across project archives, and reliable teamwork session handling for distributed designers.

How we deliver it

BIMcloud hosted on ConnektCloud Azure with managed library replication. We run the upgrade cycle against Graphisoft's release calendar so the team is on a supported version without surprise downtime.

Stack

AutoCAD + Adobe CC

Autodesk AutoCAD and Adobe Creative Cloud

What it needs

Licence pool management, deployment automation, and the workstation graphics drivers that don't break with every Adobe update.

How we deliver it

Centrally managed licence pool, deployment via Intune, and a tested driver baseline per workstation generation. New starters productive on day one, not day three.

Stack

Rhino + V-Ray

Rhinoceros 3D with V-Ray rendering

What it needs

GPU-accelerated workstations or a render node, distributed rendering across the studio, and the queue management that keeps overnight renders from collapsing the network.

How we deliver it

We design and operate the render farm or render-on-cloud setup, sized to the studio's actual production load. Queue jobs by priority so the principal's render doesn't wait behind the intern's test scene.

Stack

External sharing + reviews

Drawing release, design reviews, and consultant access

What it needs

Time-bounded external access, audit trails for every drawing release, and a workflow that doesn't depend on the model getting emailed back and forth as ZIPs.

How we deliver it

SharePoint or BIM 360 Document Management as the authoritative release surface, configured with the access model first. Every external party gets a named identity with logged access. The audit trail exists by construction.

The workstation question

A spec sheet, not a marketing brochure.

Workstation procurement is where most architecture IT decisions go wrong. The temptation to standardise on a generic SOE laptop saves money in year one and costs the practice billable hours every week after. We build the spec from the model, not from a vendor catalogue.

  • Spec built from your largest live model

    We benchmark Revit and ArchiCAD against your real models, not the vendor's published reference. CPU, RAM, GPU, and storage decisions trace back to evidence.

  • Rolling 3-to-4-year refresh cadence

    Refresh is planned and budgeted across the financial year, not triggered when a designer's machine becomes unusable mid-deadline.

  • Documented driver baseline

    Every workstation generation has a tested driver and software stack. Revit, AutoCAD, and Adobe updates land in a baseline first, not on a designer's machine on a Friday.

  • Cloud workstations where they fit

    Azure Virtual Desktop with GPU acceleration for surge capacity or remote-first staff. The economics need to work - we'll tell you when it does and when it doesn't.

  • Endpoint protection that doesn't slow renders

    We exclude render and worksharing paths from real-time scanning, tested against the actual products. No surprise 30-percent render slowdowns from default AV settings.

Customer evidence

Architecture case studies, in flight.

A multi-studio practice and a single-principal architect are both in case study production. Until then, the customer list above can speak to multi-year engagements - book a discovery call and we'll connect you with the closest reference.

Coming next

A multi-studio Revit migration and a single-principal cloud workstation deployment, both pending customer approval.

Architecture FAQ

Questions architecture practices ask us first.

We have 200GB of Revit central files. How do you host them?
On ConnektCloud Azure, on infrastructure tuned for Revit Server's IOPS profile. The performance brief includes the size of your largest live model and the number of concurrent designers, and we benchmark against your real workload, not a synthetic test. Worksharing latency targets are documented in the SLA.
Can you support Macs as well as Windows workstations?
Yes. ArchiCAD is the typical Mac workload in Australian practices. We baseline both platforms against the design-software vendor reference specs and run Jamf or Intune device management as needed. The studio's choice of Mac or PC stops being an operational problem.
Do you understand BIM 360 / Autodesk Construction Cloud?
Yes. We operate ACC for several Melbourne practices including the Document Management, Design Collaboration, and Model Coordination modules. The setup work that matters - permissions model, project templates, naming conventions - is part of the onboarding scope.
How do you handle external consultant and contractor access?
Time-bounded guest identities in Entra ID, with access scoped to the project folders they need and an audit trail of every download. Quarterly cleanup of expired access. The model where consultants get a shared password is not a model we support.
What about Adobe Creative Cloud licences? They cost a fortune.
Adobe licensing is genuinely expensive and the Creative Cloud admin console is genuinely awkward. We manage the licence pool, track active assignments, and reclaim seats from departing staff in the same cadence as the offboarding process. Most practices recover 10-15 percent of their Adobe spend in the first year.
We're doing a studio fit-out. Can you handle the network?
Yes. Studio fit-outs are one of our standard projects - cabling spec, UniFi network design, workstation positioning, meeting room AV, and the patch panel layout that doesn't make the next change a disaster. We work directly with your builder and AV installer so the studio is operational from day one.
Ready when you are

Leave the MSP that doesn’t pick up.

Tell us what your current setup looks like. We’ll send back a quote, a transition plan, and a firm date you’d be onboarded - within 48 hours.

Response
Within 48 hours
Format
Written quote
Discovery call
Not required
Contracts
No lock-in terms

We’ll respond within 48 business hours. No spam, ever.