QuickBooks + Drake on One Server: The Hosting Architecture Most Firms Get Wrong

QuickBooks + Drake on One Server: The Hosting Architecture Most Firms Get Wrong

If you’re a tax firm running QuickBooks Desktop and Drake Tax, you’ve probably asked the same question every other firm owner asks. Can these two apps actually live on the same hosted server? Or are you stuck with one login for QuickBooks, another for Drake, and workflows that fight each other?

The short answer is yes. On a properly built dedicated server, QuickBooks and Drake run side by side without compromise. The longer answer is the reason this question comes up at all. Most shared hosting providers split them across different back-end clusters by default. That’s where the real problems start.

This post walks through what “same server” actually means, the hidden cost of splitting QuickBooks and Drake, how to size a dedicated server for both, and what to ask any provider before you sign a contract.

TL;DR

Yes, QuickBooks and Drake can run on the same hosted server. On a dedicated single-tenant server, it’s the baseline. On RightWorks and other multi-tenant providers, your QuickBooks user and Drake user often land on different back-end servers, which introduces input lag, blocks add-ons like TicTie Calculate, and turns simple workflows into support tickets. If integrations matter, if you have more than five concurrent users, or if you’re subject to the FTC Safeguards Rule, a dedicated server is the right answer.

Why firms ask if QuickBooks and Drake can run on the same hosted server

Every tax firm runs two kinds of software. A general ledger platform, usually QuickBooks Desktop or Enterprise. And a tax package. Drake is common. So are Lacerte, UltraTax CS, and ProSeries. Layer in document management, a PDF tool like TicTie Calculate, payroll, a client portal, and a CRM, and you’ve got eight to twelve hosted applications that need to talk to each other.

The instinct to ask “can these all live on one server?” doesn’t come from nowhere. It comes from real pain on shared hosts.

Firms on RightWorks report half-second input delays during tax season. A Reddit thread in r/Accounting from October 2025 describes tasks that should take ten seconds stretching to thirty. A Drake customer on r/taxpros notes “a slight delay compared to local hosting” while paying more than $5,000 a year. Integrations that worked locally start throwing connection errors when QuickBooks is on one hosted cluster and the add-on is on another. Drake multi-user setups hit a “drive letter A-Z” error. QuickBooks updates that Intuit released two weeks ago haven’t been applied to the hosted image. Support tickets auto-close at 3 AM with no resolution.

None of this is Drake’s fault. None of it is QuickBooks’ fault. It’s an architecture problem. And the fix is to run both apps on one dedicated server instead of splitting them across a multi-tenant fleet.

Three ways to host QuickBooks and Drake together

Before we get into the cost of getting this wrong, let’s name the three models a firm can actually choose from.

Model 1: Local, on-premise

Both apps live on a server in your office closet. Fast local access. No cloud latency. You own every compliance burden: your WISP, your backups, your MFA setup, your patching cadence, your physical security. If the box dies, your firm stops. If the building floods, your data floods with it.

This is where most firms started. It’s also where fewer and fewer of them are finishing. IRS Publication 4557 and the FTC Safeguards Rule both push toward documented controls that are easier to prove on a managed cloud than on a closet server. The trend away from on-prem is real, and it isn’t reversing.

Model 2: Multi-tenant shared cloud (the RightWorks model)

You get access to a pool of shared servers, identified by cryptic names like BPOLCP02.rightworks.com or VPOLCP001.rightworks.com. Your QuickBooks license lives on one cluster. Your Drake license might live on a different one. You log in through AppHub, but each app opens its own RDP session against its assigned back-end host.

This is cheap per seat for the provider. It’s also where the compounding problems live. Because the servers are shared across hundreds of firms, the host has to tightly control what gets installed. That’s why RightWorks runs a restricted application catalog. If the add-on your workflow depends on isn’t on the approved list, you can’t install it. Period. TicTie Calculate is one of those tools. So are a long list of other QuickBooks and PDF add-ons that firms use every day.

Model 3: Dedicated single-tenant cloud (the VeritSpace model)

One server, provisioned for your firm only. QuickBooks, Drake, Lacerte, UltraTax, TicTie Calculate, Bill.com, your document management system, whatever else you run. All on the same machine, under one login. No cluster hops. No noisy neighbor. Resources are yours.

This is the model Verito runs. It’s more expensive per user than shared hosting. It pays for itself the first time tax season hits and nothing slows down.

What it actually costs when QuickBooks and Drake live on separate servers

On paper, a half-second of input lag doesn’t sound like a crisis. Run the math and it becomes one.

A working preparer clicks, tabs, or types at least 1,200 distinct inputs per hour during active tax prep. Call it conservative at 1,000. If each one incurs an extra half second, that’s eight minutes of pure lag per hour. Over an eight-hour day, you lose more than an hour per preparer. Multiply by ten preparers. Multiply by 120 days of active tax season. That’s 1,200 hours of billable capacity burned on round-trip latency. At any reasonable billing rate, the dollar figure is five figures. Per year. Before you’ve accounted for staff frustration, missed deadlines, or the client calls you didn’t make.

That’s just the lag. The other failure modes are worse.

Add-ons that can’t be installed at all. This is the one most firms don’t see coming. RightWorks’ shared server model requires a restricted application catalog, because anything one firm installs runs on infrastructure other firms use. If your add-on isn’t on the approved list, you can’t run it on RightWorks. TicTie Calculate, the audit tickmark and PDF annotation tool from Wolters Kluwer CCH that many preparers and auditors rely on, is a well-known example. A long list of other QuickBooks add-ons, custom ODBC reporting tools, vertical-specific integrations, and internal utilities firms have built over the years are restricted for the same architectural reason. On a dedicated server, the catalog question doesn’t exist. If the software runs on Windows, you install it.

Drake network drive errors. Drake requires a mapped drive letter between A and Z for multi-user access. That’s a hard requirement. When a shared host provisions your “server” user on one hosted machine and your “workstation” users on another, the drive mapping breaks after every RDP session restart. The fix, per Drake’s own KB, is to map the drive with “Reconnect at sign-in” enabled on every workstation. That’s a fix, not a feature. On a dedicated server where every Drake user logs into the same machine, the problem never shows up.

QuickBooks update lag. Intuit releases a QuickBooks patch on a Tuesday. On a shared host, the provider patches their hosted image on their own schedule, which might be the following week. One G2 reviewer in July 2025 spent three and a half hours on a call with RightWorks trying to get a two-week-old QuickBooks update applied. Their ticket auto-closed at 3 AM with no resolution. On a dedicated server, your host patches your machine when you ask, not when it fits their release calendar.

Support hand-offs. When QuickBooks is on cluster A, Drake is on cluster B, and an integration is broken, every support conversation starts with “which vendor owns this?” The answer on a multi-tenant host is almost always “the other one.” That’s not the host being difficult. That’s the architecture generating the hand-off.

Storage caps and archive costs. Most shared hosts meter storage per user and bill overages. RightWorks caps each user at 40 GB and charges $1 per additional gigabyte. Tax firms archive prior-year Drake files, scanned source documents, audit workpapers, and QuickBooks backups. A three-year archive for a ten-preparer firm can easily blow past the default allocation. On a dedicated server, you size the disk once and grow it when you need to, without the per-user accounting.

The security trade-off nobody talks about. Multi-tenant hosts often expose raw RDP on port 3389 to the internet, with MFA as the only guard. That’s a documented IT-sysadmin objection about the RightWorks architecture, raised publicly in late 2024. A dedicated server can sit behind a VPN or zero-trust gateway, which is a different posture and a different conversation with your cyber insurer.

How to size a dedicated server for QuickBooks and Drake

If you’re evaluating dedicated hosting, the next question is practical. How much server do you actually need?

Here’s a useful tell about how to think about this. Most providers answer in RAM and vCPU. That’s the spec-sheet answer. The more useful answer is two-axis: how many seats you need (headcount) and how intensive your app mix is (workload). Tier by headcount alone is a lazy mapping.

Verito sizes VeritSpace around three tiers, with NVMe storage standard across all of them:

A note on solos and two-preparer firms. Dedicated hosting carries fixed infrastructure costs that don’t shrink with headcount. A one-person shop pays for the same underlying server as a five-person team. The math works cleanly once three or more preparers share the resource, because that’s when concurrent workload, app density, and performance headroom start to matter. We’re happy to host solos who want the isolation, the compliance posture, and the performance of dedicated infrastructure. Just know the per-user math tilts harder against you the smaller the team, and an honest comparison against shared hosting should include that.

A few sizing rules of thumb worth knowing whatever tier you land on.

Drake multi-user setup depends on NW Client versus peer-to-peer. NW Client keeps one Drake install on the “server” and has every workstation connect to it. Peer-to-peer installs Drake on every user’s workstation and has them share data. NW Client is easier to update and easier to host on a dedicated server. Peer-to-peer requires installing state modules on every workstation separately, since state modules can’t be shared from the server.

QuickBooks multi-user needs the file on local disk. QuickBooks Database Server Manager expects the company file to live on the server’s local drive, not on a mapped network drive. On a dedicated server, this is the default. On a shared host that provisions your users on different machines, you have to ask support to consolidate you.

Dedicated servers scale linearly. Add a user, add the tier headroom they need. Multi-tenant shared hosts don’t work that way. Your performance is a function of whatever other tenants are doing at 3 PM on April 14.

A simple decision framework for multi-app tax hosting

Here’s the flow. Work down the list in order and stop at the first hard yes.

Do you run QuickBooks add-ons or any software outside the big-name catalog? If yes, you need a dedicated server. TicTie Calculate, niche industry tools, custom ODBC reports, internal utilities, and plenty of QuickBooks add-ons are restricted on RightWorks’ shared environment and simply can’t be installed there. On a dedicated server, there’s no approval catalog. If it runs on Windows, you install it on your server.

Do you have more than five concurrent users on Drake? If yes, go dedicated. Drake multi-user on shared infrastructure gets expensive fast, and the drive mapping and state module issues compound with every additional workstation.

Are you subject to the FTC Safeguards Rule (20+ preparers, or any firm whose insurer is asking)? Dedicated simplifies the documentation. Your WISP names a specific server with specific controls. 

Are you a solo or two-person shop? Dedicated hosting works for you, but the per-user math tilts harder the smaller the team, because infrastructure costs are fixed. Three preparers or more is where concurrent workload and app density start to pay for the dedicated resource. Run the numbers with that in mind before you sign anywhere.

Do you already have your own IT team and a data center relationship? Local on-prem is still viable at the high end. Just know that every compliance responsibility is yours, and the FTC’s documentation expectations aren’t getting lighter.

Everyone else, which is most firms between three and fifty preparers, is better off on a dedicated hosted server.

How Verito runs QuickBooks and Drake on one dedicated server

We built VeritSpace around one idea. A tax firm’s apps should all live on the same machine, with the same performance profile, under one login, supported by humans who actually answer the phone.

One server, your firm only. We provision a dedicated Windows Server for your firm. QuickBooks Desktop or Enterprise, Drake Tax, Lacerte, UltraTax, ProSeries, TicTie Calculate, document management, payroll, Bill.com, and whatever else you run all install on that one machine. No clusters. No cross-server hops. When your staff launches Drake and QuickBooks in the same session, they’re literally running on the same CPU.

Support that picks up. A real person answers in under 60 seconds. Our first-touch resolution rate is 92%. Our NPS is 95. Our G2 score is 4.9 out of 5 across more than 150 reviews. When something breaks, one human owns it from ticket open to ticket close. No auto-closures at 3 AM.

Performance we can defend. Independent benchmarks put VeritSpace at 35% faster than standard shared hosting on equivalent workloads. We’ve held 100% uptime since we launched in 2016. Tax season doesn’t degrade the experience because you’re not sharing resources with 500 other firms.

Compliance documentation included. Every VeritSpace instance ships with FTC Safeguards Rule documentation, IRS Publication 4557 alignment, WISP coverage, MFA, encryption at rest and in transit, and the audit trail your insurer wants to see. We don’t charge extra for this. It’s the baseline.

Migration in 24 to 48 hours. Our onboariding team moves your data, installs your apps, maps your users, and runs parallel access until you’re ready to cut over. One named onboarding contact runs the whole thing. You don’t have to coordinate between three vendors.

Here’s what a typical switch looks like from your side. You tell us which apps you run and how many users. We stand up your VeritSpace server and pre-install the software. We schedule a two-hour window, usually after hours, to copy your QuickBooks company files, your Drake data folders, any TicTie Calculate workpapers, and your document archives. We install your staff’s login shortcuts and test one user end to end. The next morning, your team logs in and everything is where they left it. We leave your old environment running in parallel for a week, so if anything is missing or someone needs an old file, it’s a click away. After the parallel week, we decommission the old environment on your go-ahead. No data stranded on a cluster you can’t reach.

Storage and compute that scale with you. No 40 GB per user cap. No $1 per GB overage. Need more RAM for a memory-heavy workload? $20 per GB. Need another 10 GB of storage for a multi-year archive? $10. Need to run an extra app beyond your tier’s allotment? $10 per month. Line-item transparent. No surprises on the next invoice.

What we don’t do: shared clusters, multi-tenant servers, off-hours ticket queues, or storage overages at $1 per gigabyte. The architecture is the product.

Questions to ask any hosting provider before you sign

The seven-question pre-signature checklist

1. Is this a dedicated server for my firm only, or a shared multi-tenant environment?
2. Will QuickBooks and my tax software run on the same physical machine? Get it in writing.
3. What’s the first-response SLA in writing? Is support 24/7, or business hours only?
4. Do you provide FTC Safeguards and IRS WISP documentation I can hand to my insurer?
5. When Intuit releases a QuickBooks patch, when does my instance get patched?
6. What’s the backup retention, recovery SLA, and documented DR procedure?
7. What does the cancellation process look like, and is it in writing?

If a provider can’t answer any of the seven in writing, keep shopping. If they can answer six but not the architecture question, you’re looking at a shared host that’s going to split your apps across clusters sooner or later. The cost of finding that out after you’ve migrated is worse than the cost of one more evaluation call.

Pay extra attention to question two. Some shared providers will agree to co-locate your users “best effort” but won’t put it in the contract. Best effort is not a guarantee. It’s a statement of intent that expires the moment their capacity planning changes. Ask for the architecture commitment in writing, with a named remedy if it’s ever violated. A provider who can’t or won’t do that is telling you what you need to know.

The bottom line

Can you run QuickBooks and Drake on the same hosted server? Yes. On a dedicated server, it’s the default. On shared multi-tenant infrastructure, it’s an exception you have to fight for, ticket by ticket, release by release, tax season by tax season.

The firms that quietly pull ahead in the next few years won’t be the ones who found the cheapest per-seat host. They’ll be the ones whose infrastructure gets out of the way so their preparers can do the work.

If you’re running QuickBooks and Drake together and you want both on one dedicated server, with a real human on the other end of the phone, book a 20-minute VeritSpace walkthrough. We’ll show you exactly how it’s configured and what migration looks like for a firm your size.

Frequently Asked Questions

Can QuickBooks Desktop and Drake Tax run on the same hosted server?

Yes, on a dedicated single-tenant server. Both applications install on the same Windows Server, share one login, and run under the same session. On multi-tenant shared hosts like RightWorks, the two apps often land on different back-end clusters by default, which is what causes the input lag, add-on restrictions, and support hand-offs firms complain about.

Why do shared hosts split QuickBooks and Drake across different servers?

Multi-tenant hosts provision user accounts across a pool of shared servers to balance load. Your QuickBooks license may get assigned to one cluster and your tax software license to another based on capacity, not on what your workflow needs. The host may offer to co-locate you “best effort,” but without a written architecture commitment that assignment can change with the next capacity plan.

Is TicTie Calculate compatible with shared hosting like RightWorks?

Not reliably. Shared hosts run restricted application catalogs because anything installed affects infrastructure shared with other firms. TicTie Calculate, most QuickBooks add-ons, custom ODBC reporting tools, and internal utilities are commonly outside that catalog and can’t be installed. On a dedicated single-tenant server there is no approval catalog: if it runs on Windows, you install it.

How much RAM does a QuickBooks + Drake hosted server need?

RAM and vCPU are the spec-sheet answer. The better answer is two-axis: headcount plus app intensity. A three-to-five preparer firm running QuickBooks plus one tax package is an Essentials tier on VeritSpace. Six to twenty preparers running QuickBooks, Drake, TicTie Calculate, a portal, and document management sit on Pro. Heavy workloads, UltraTax engagements, or large QuickBooks Enterprise files push toward Elite. Add-ons are available a la carte: $20 per extra GB of RAM, $10 per 10 GB of storage, $10 per extra app per month.

How long does it take to migrate from RightWorks to a dedicated server?

On VeritSpace the standard migration runs 24 to 48 hours end to end. One named onboarding contact stages the new server, pre-installs your apps, copies your QuickBooks company files, Drake data folders, TicTie Calculate workpapers, and document archives during a two-hour after-hours window, and runs parallel access to your old environment for a week so nothing is stranded on a cluster you can’t reach.