Your outsourced IT team: we run the help desk, maintain servers and monitor backups — remote and onsite. For production studios we also run the render farm: Deadline, plugin versions, storage and overnight renders. We don’t sell licenses — setup, tuning and upkeep only.
Two doors in, the same way of working: day-to-day IT for companies and render infrastructure for studios. Everything we do is written down — and stays yours.
01
IT support for companies
An outsourced IT team: remote and onsite help desk, computers, network, servers and backup. One place to call when something stops — and a documented system instead of a black box.
Regular upkeep of servers and services: scheduled updates, monitoring, backup checks and interventions. A monthly report on the state of things and an up-to-date inventory.
Faults reported through a ticket, email or phone; we resolve them remotely, and onsite when needed. Workstations built from a standard image, ready on day one.
A fault is reported once and has an owner.
04
Backup monitoring
A daily check that backup jobs completed, and periodic test restores with a written record. MIODATA designs the backup architecture; we keep it running.
A backup proven by restore, not assumed.
05
Onsite work and cabling
Deploying workstations, printers and network gear, Wi-Fi coverage, office cabling and relocations. The same documented way, every time.
When you need someone on the spot.
06
Render farm and pipeline
Deadline, the same software and plugin versions on every node, a license server with a standby, and storage the farm can see. We don’t sell licenses — setup and upkeep only.
Your best artist shouldn’t have to be the sysadmin.
What IT with an owner looks like — drawn, not described.
This is what a typical environment under our support looks like: your office stays yours, while reports, monitoring and onsite work follow a clear path — with a paper trail.
FIG. 01 — One team for your IT
Illustration — schematic, not to scaleMA-01
What it looks like inside
01
Your office
Workstations, the server and the network stay with you. We inventory them, document them and keep them running.
02
Help desk
Faults are reported through a ticket, email or phone. One address — so every report has an owner and a history.
03
Monitoring
Servers, disks and backup jobs are watched. The alert reaches an engineer before a user feels the problem.
04
Onsite by contract
What can’t be done remotely is done in person: equipment installs, cabling, relocations, preventive visits.
The schematic illustrates a typical setup; it is not a snapshot of any client environment.
03›manajo cases --anonanonymized
Where this makes sense
One delivered job and two typical engagements — a description of how we handle them, clearly labeled. No names and no numbers.
Creative studio · delivered work
A studio with huge files
Situation
A creative studio works with large files: everyone has access to everything, the archive is scattered, and nobody has proven the backup with a restore.
Approach
A review of the NAS, folder structure and rights — no changes. Then a project structure with per-team access; MIODATA designed the backup architecture, and we monitor it daily.
Resolution
Files are seen by the right people, the archive has order, and the backup is known to restore — a test restore was performed and recorded. We still administer the studio.
Typical engagement · how we handle it
A company with no internal IT
Situation
Nobody owns IT: whoever is free handles the breakdown, nobody checks the backup, and nothing says how anything was set up.
Approach
Takeover starts with an inventory and documentation, without a single change. Then a help desk as the one place to report to, servers and backup under monitoring, and a test restore.
Resolution
One owner for IT and one address for everything; a backup proven by a test restore; a monthly report management can read. This describes our procedure, not delivered work.
Typical engagement · how we handle it
The render dies on the last frame
Situation
Batch renders stop without a clear cause, a node is up but jobs won’t start, and the farm sits unused after hours.
Approach
A no-change review of the farm: software and plugin versions per node, Deadline pools and priorities, asset paths, the license server. Then version alignment and a night queue.
Resolution
The same versions on every node, jobs scheduled by deadline, and a farm that actually works overnight — with a version list that is kept up to date. This describes our procedure, not delivered work.
Partners we work with and clients whose systems we build and maintain.
07partners
07clients
Names only — no logos and no numbers. The list is the whole reference.
Partners
07
ABAPASS
WOWA
AMAI
CARBON
MONTWIN
SIGNET
SAMPRO
Clients
07
SC TAŠMAJDAN
FRAJNI DOO
DREAMTIME
ALFACO
HEMA-KHEYA-NEYE
ROYAL BUILDING
ZAMBA
We collaborate with partners; for clients we build and maintain systems — support, maintenance and rendering.
Case notes stay anonymous — names on this list and the engagements described are not paired.
The only number we highlight: 20+ years of experience. Let the list say the rest.
05›moya policy --read-onlyread-only
Your systems are yours. We work by rules you can check.
When you give us access to a server, network or database, you give us trust. These rules apply to every job, equally for MOYAGRID, MIODATA and MANAJO.
01
Read-only by default
Every access starts as read-only: we look at configurations, logs and state, and change nothing. The right to change is granted separately, per specific change.
02
Approval for every change
We describe what we’ll change, why, and what could go wrong. Approval covers that change — not the next one. Silence is not approval.
03
Backup before every change
Before changing a configuration, file or database, we make a dated copy of the previous state. No exceptions, even when the change is “just one line”.
04
Every change has a way back
Each change comes with how to roll it back and how long that takes. If we don’t know how to roll it back, we don’t do it.
Workflow · MANAJONo-change IT health check → takeover and documentation → regular maintenance and monitoring → monthly report
We look at your systems — servers, backup, network or the farm — and write a concrete assessment: what’s fragile, what’s slowing you down and what’s worth fixing first. The review changes nothing, and the report stays yours even if we don’t continue.