DesksShared

Every desk,every hour.

Your studio already owns the machines. DesksShared lets staff work from home on their own office workstation, then lends the idle ones to colleagues, approved freelancers and overnight render jobs. IT sets who gets what, and when.

Files stay on your machines. Nothing is copied to a cloud.

IdleIn use by Anika (remote)IdleOvernight render jobAnika, at home
Built for studios that run on heavy machines

Tuesday, 9:40 pm, Pune

Forty workstations. Thirty-one of them asleep.

The lights are off in the studio. Each desk has a machine with a big graphics card and 64 GB of memory that cost more than a small car. Most of them have done nothing since 7 pm.

Meanwhile Anika, a senior designer, is at home in Kothrud with a thin laptop that cannot open the Revit model. A freelancer the studio trusts needs a GPU for two nights. And the walkthrough render for Thursday's client meeting is still waiting for a free machine.

DesksShared connects those three problems to the machines you already paid for.

How it works

Three steps, one afternoon of setup.

01

Install the host app

A small app goes on each office PC. It checks the GPU, the network and whether anyone is sitting at the desk.

02

Write the rules

IT decides which machines are shared, with whom, and in which hours. Outside users stay off until you turn them on.

03

People connect

Staff open their own desk from home. Others book a free machine. Every session is logged with who, which PC, and how long.

For your staff

Your own desk, from your dining table.

Open your office workstation from home and keep working where you left off: same files, same plugins, same licences. Viewport rotation should feel like you are sitting in front of it.

  • Low latency on ordinary broadband. Video is encoded on the office GPU and adapts to your connection.
  • Pen tablets and two monitors. Pressure works, and your home screens map to the office ones.
  • Colour you can trust. A 4:4:4 mode for colour work, when your line can carry it.
  • Your desk stays yours. In working hours nobody else can book the machine assigned to you.

Sample Session window with made-up project data.

One workstation, one day

Nine hours of work. Fifteen more on the table.

  1. Staff at homeAnika opens her own desk remotely09:00–18:00
  2. Freelancer: RaviApproved by the studio, booked for the evening18:00–23:00
  3. Render agentOvernight frames for Thursday's walkthrough23:00–06:00
  4. Back to its ownerUpdates, cool-down, ready by morning06:00–09:00
0003060912151821
09:00
Staff at home
Utilisation todaySample
88%
21 of 24 hours in use

One machine. Three kinds of user.

The same office PC can serve the person it belongs to, a trusted outsider and a piece of software. Each gets a separate login, a separate time window and a separate log.

People at homeYour staff, on their own desk
Approved freelancersOnly if you allow outsiders
Agents and batch jobsRenders, sims, model training
Who it's for

Each person sees only what you allow.

Staff: your desk follows you home

Each person is tied to their own workstation. From home they see one button: connect to my desk. If their desk is busy or broken, IT can point them to a spare in two clicks.

They can

  • Open their own PC any time in working hours
  • Use a pen tablet and two screens
  • Book a second, bigger machine for a heavy day

They cannot

  • Open someone else's desk without a booking
  • Copy files to their laptop, if IT turns that off
  • Keep a booked machine past its end time
For IT teams

The whole floor, on one screen.

See every workstation, who is on it, what its GPU is doing and when it frees up. Move a booking, end a session or take a machine out of the pool for repairs.

DesksShared
All 40In use 22Free 11Booked 5Offline 2
Sample
Machines in pool40
In use now22
Render jobs queued7
Outside usersOff
MachineGPUStatusUsed byGPU loadUntil
WS-14Floor 2 · Arch teamRTX A4000 16 GBStaff remoteAnika R.46%18:00
WS-09Floor 2 · InteriorsRTX 4080 16 GBFreelancerRavi K.31%23:00
WS-23Render bayRTX 4090 24 GBRender jobrender-agent-297%06:00
WS-31Floor 3 · VizRTX A5000 24 GBAt deskMeera S.62%–
WS-17Floor 2 · Arch teamRTX A4000 16 GBFree–2%–
WS-05Floor 1 · MEPRTX 3060 12 GBOffline––Repair
Rules and schedules

Who gets what, written down once.

Rules are plain sentences with a time window and a switch. When two rules clash, the stricter one wins and IT gets a note.

A person at the keyboard always comes first. If someone sits down at a shared machine, the remote session gets a two-minute warning and then hands over.

09:00–18:00Mon to Sat

Assigned desks open only to their owner, from office or home.

18:00–23:00Weekdays

Idle machines on Floor 2 can be booked by any staff member.

18:00–23:00Weekdays

Approved freelancers may book up to 4 machines from the evening pool.

23:00–06:00Every night

Render bay machines go to the job queue. Hard stop at 06:00.

SundaysAll day

Machines stay off the pool for Windows updates and backups.

Sample Rule list for a made-up 40-seat studio.

Overnight jobs

Hand the night shift to software.

Queue renders, simulations or AI agents that need a desktop. DesksShared hands each job a free machine that matches what it needs, watches the clock and stops it before staff arrive.

  • Match the job to the GPU. A job that needs 24 GB of video memory only lands on cards that have it.
  • Pause, then resume. Jobs that support checkpoints pick up the next night where they stopped.
  • Command line and API. Plug into the render manager or scripts you already use.
Tonight's queue · 23:00 to 06:00Sample
Clubhouse walkthrough, frames 1–900WS-23 · RTX 4090 · started 23:04Running
Facade daylight studyWS-24 · RTX 4090 · started 23:05Done 02:18
Chair texture variants (agent)WS-26 · RTX A5000 · started 23:30Running
CFD airflow, lobbyNeeds 24 GB · waiting for a machineQueued
Turntable, product BWS-21 · reached 06:00 stopPaused
# queue a render for tonight (sample) desks job add "clubhouse-walkthrough" \ --gpu-mem 24 --window 23:00-06:00 \ --run "blender -b scene.blend -a"
Trust and security

Your files stay in your building.

Remote users see a video stream of the screen. The project files never leave the workstation unless you allow it.

No cloud copy

DesksShared does not sync, upload or back up your files. They stay on your PCs and your file server.

Your sign-in, your roles

Log in with your studio's Google Workspace or Microsoft account. Two-step sign-in for every outside user.

Clipboard, files and print, per rule

Turn copy-paste, file transfer and printing on or off for each group. Freelancers start with all three off.

A log of every session

Who connected, to which machine, from where, for how long. Export it as CSV for your own records.

Encrypted end to end

Sessions are encrypted between the two devices. Our relay only helps them find each other.

A kill switch

IT can end any session, or every session, from the console. The host app also obeys a local off switch.

Plainly

What DesksShared does not do.

We would rather lose a sale now than have you find out in month two.

  • It does not move your files to the cloud.No storage, no sync. If a machine is off, its files are out of reach.
  • It does not work on Wi-Fi-only machines.Every host PC needs a wired network connection.
  • It cannot make a small GPU do a big job.A machine is only lent for work its graphics card can actually handle.
  • It does not decide who your outside users are.The studio chooses whether outsiders are allowed at all, and invites each one by name.
  • It does not sell your spare hours to strangers.There is no public marketplace. The pool is yours.
  • It does not cover software licences.Check that your licences allow remote and after-hours use.
What you need

Check these four before you call us.

Host PCsWindows 10 or 11

Workstations with an NVIDIA or AMD card from the last few years. Linux hosts are on our list.

NetworkWired, every host

Gigabit Ethernet in the office. Remote users need a steady broadband line, ideally 20 Mbps or more.

PowerMachines left on

Or Wake-on-LAN set up, so the pool can wake a sleeping PC for a booking.

PeopleOne IT owner

Someone in the studio who sets the rules and approves outside users.

Do the maths

Turn your workstations into infrastructure.

Before you buy a render farm or rent cloud GPUs, count the hours your own machines already sit idle. Move the sliders to match your studio.

40
9
24
14,400

idle machine-hours a month on working days, before weekends. This is arithmetic from your inputs, not a promise of how many you can use.

How we charge

Per machine, per month.

Pricing is on request while we work with our first studios. The shape of it is simple, and we will put the number in writing before you install anything.

Host licenceper workstation

A monthly fee for each PC in the pool, billed in ₹ with GST. Remote users are not counted.

Outside usersno extra seat fee

Freelancers you invite do not add a charge. You decide what, if anything, to bill them.

Render and agent hoursincluded

Jobs run on your own hardware, so we do not meter them.

Setup helpon request

We can set up the first ten machines with your IT person on a call.

FAQ

Questions IT usually asks first.

What happens if someone walks up to a machine that is lent out?

The person at the keyboard wins. The remote user or job gets a two-minute warning, then the session hands over. Jobs that support checkpoints save their progress first.

Can a freelancer see our other projects?

Not if you set it up as we suggest. Outside users get a separate Windows profile with only the folders you share, and clipboard, file transfer and printing start switched off.

Does it work over a home Wi-Fi connection?

On the remote side, yes. Home users can be on Wi-Fi or mobile data, though a steady line gives a smoother picture. The office PC itself must be wired.

Will it slow down the machine when the owner is using it?

When the owner sits at the desk, the host app stays quiet. It only encodes video during a remote session, and uses the GPU's built-in encoder for that.

Are our software licences fine with this?

That depends on your vendor and contract. Many design tools allow remote use by the licensed person; after-hours use by others can need a different licence. Please check before you open the pool to freelancers.

Where is the data about sessions kept?

Session logs and account details are stored by us so the console works. Your project files are never part of that. The privacy notice explains what we keep and for how long.

Can we try it on a few machines first?

Yes. Most studios start with five to ten PCs and staff-only access, then add evening and overnight rules once they trust it.

Talk to our team.

Tell us how many workstations you have and what keeps them busy. We will set up a 30-minute walkthrough with your IT person and answer the awkward questions.

We use these details only to reply. See the privacy notice.