# Minicor

Official pricing: https://minicor.com  
Category: windows · Isolation: dedicated-vm

## Pricing regimes (raw)

- **Native product; see regime notes** (resource) [alt]

## Features

Yes: persistent disk, ≥24 h sessions, full VM (own kernel), browser, desktop GUI, computer-use API, browser + desktop control, HTTPS preview URLs, egress allowlist, self-hosting, BYOC, SOC 2, HIPAA, Windows, MCP server, hosted agent API (their own agent), gVisor or VM (no shared kernel), inbound access rules, firewall inside (nftables)

No: snapshots, memory snapshots, fork/clone, pause/resume, volumes, idle auto-stop, start from your own snapshot, your own Docker/OCI image, Docker inside, nested virtualization, anti-bot stealth, CAPTCHA solving, preinstalled agents, SSH, open source, GPU, arm64, macOS, Python, Node.js, HTTP method/path egress rules, wake on request, live resize, live fork (no pause), memory fork, EU data residency, automatic snapshots, snapshots on demand, agent harness API, secret proxy, secret proxy for any API, extra volumes, shared volumes

Unknown: everything else. Evidence (source + quote) per feature: https://battleships.dev/data/providers/minicor.json → feature_evidence

## Caveats

- Public enterprise desktop-automation product; YC explicitly says scalable Windows desktop automation/VM. Quote-led offering, no verified Windows CPU/RAM/license-inclusive tariff. Product website sign-in/demo does not prove self-serve availability.
- Null values mean unknown, not free/unlimited. No model-token cost, tax or unverified ancillary charge included.
- Native browser/device/task/credit prices with unknown CPU/RAM are deliberately non-priceable. Check regime before interpreting any partial resource estimate.

## How this provider charges


YC: Spring 2026; directory status **Active**. Research scope: public-product-researched. Source: https://www.ycombinator.com/companies/minicor

Windows desktop automation

## Regime table

| Regime | When it applies | How billed | Numbers | Source |
|---|---|---|---|---|
| Native product; see regime notes | Incomplete or non-resource economics: rates remain null, never interpreted as free. | resource; CPU alloc, memory alloc | Unknown or native-unit billing; see facts below | https://minicor.com |
| Current applicable tariff unverified | Plan limits apply | Monthly fee; credits only as stated | fee=None; included usage=$None; concurrent=None; max session h=None | https://minicor.com |
| Retained disk / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://minicor.com |
| Snapshots / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://minicor.com |
| Egress / GiB | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://minicor.com |
| IPv4 / month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://minicor.com |

## Verified billing facts and gotchas

1. Public enterprise desktop-automation product; YC explicitly says scalable Windows desktop automation/VM. Quote-led offering, no verified Windows CPU/RAM/license-inclusive tariff. Product website sign-in/demo does not prove self-serve availability.

## Worked example

Requested: 4 vCPU/8 GiB, 50 simultaneous × 8 h/day × 22 days = **8,800 instance-hours**, 30% CPU; 50 GiB snapshots and 100 GiB egress. A month is 730 hours only when explicitly used in rate conversion.

**Total: unknown.** This product does not publish a verified complete 4-vCPU/8-GiB tariff and/or the service bills a different unit. Fifty concurrent instances and eight-hour sessions are not automatically supported. Neither 30% utilization nor retained snapshots can be converted into free resources. Use the native plan terms above and request the missing CPU/RAM, retention, egress and concurrency quote.

## Sources and coverage

- https://www.ycombinator.com/companies/minicor
- https://minicor.com/
- https://minicor.com/llms.txt

Page captures and documentation indexes/bundles are in `raw/`; provider JSON lists the evidence paths. HN query results were captured separately as `<id>--hn.txt`; they are discovery leads, not current tariff authority. Downloaded docs do not imply every feature was verified; unsupported assertions remain null.