DUOLABS
Our Services

In-house Infrastructure

From choosing equipment to installation, security setup, and documentation. Accounts, access, and backups stay organized, so operations survive staff changes.

Timeline
1~3 weeks
Build cost
₩2.5M~8M
Time to start
Same day to a few days

Who this fits

  • Companies whose files live scattered across personal PCs and consumer cloud accounts
  • Companies that take backups but have never actually restored one
  • Organizations with no IT staff, where one person is the only one who knows the servers, accounts, and passwords

How far we take it

Included

  • Choosing the hardware and designing the setup
  • File server or NAS installation with a folder and permission structure
  • Backup configuration plus an actual restore rehearsal
  • Business email and an account scheme
  • VPN for access from outside the office
  • Handover of accounts, credentials, and configuration docs

Not included

  • Hardware purchases and software license fees
  • Internet line contracts and telecom charges
  • A full-time on-site IT operator
  • Electrical work, cabling, and other facility construction

Build cost by scope

ScopeBuild cost
EssentialNAS & basic backup₩2.5M~4.7M
StandardServer, VPN & off-site backup₩3.9M~6.6M
AdvancedMigration, segmentation & monitoring₩5.5M~8M

These are example ranges. Once requirements are confirmed you get a fixed quote. Maintenance is billed separately as a monthly plan.

These figures are current as of August 2026. The latest ranges are on the pricing page.

How it runs

  1. 01

    Discovery

    We define the core user problem and align on scope and priorities.

  2. 02

    Design

    We design the structure and flows, validating fast with prototypes.

  3. 03

    Build

    We build maintainable systems with tests and code review.

  4. 04

    Launch

    We ship reliably with release automation and store submission.

  5. 05

    Operate

    We operate long-term with observability, logs, and metrics.

Frequently asked questions

Often it is. On-premise hardware makes sense when you handle large files daily (drawings, video, camera originals), when a rule forbids storing data outside, or when the connection is slow enough to make work painful. Otherwise the cloud has less to manage and is the better answer. We look at your actual usage and tell you which.

Having backups and being able to restore are different things. Part of what we do is perform one real restore: not a single file, but rolling back to a point in time. That is where you find out the backup has been failing for days, or that the key needed to restore lives only inside the backup. There is no way to know without trying.

We set it up assuming that will happen. Accounts and permissions are built around roles rather than a person's name, and credentials live somewhere shareable instead of in one person's memory. The configuration and restore procedure are written down. The test for a proper handover is that we are not the only ones who can run what we built.

We plan so that it does not. The existing setup stays running while the new one is built alongside it, and we switch when it is ready. Cutover usually happens outside working hours. Changing mail or the account scheme can involve a brief gap, so we tell you when and how long before picking the date.

Related public docs

Proposals, scope guides, and build examples we publish openly.

See all public docs

A vague scope is fine

Tell us where things stand and we will point to the scope you need and a rough size.