CORESERVER V2
coreserver.jp · Compute · 1 record · JSON
CORESERVER V2 Compute
caveatcardcardDwrite-gated
| Free tier | CORE-X is JPY 830 a month on the monthly subscription, JPY 610 a month on a twelve-month term and JPY 430 on thirty-six months, and the vendor's feature table gives it a 6 GB memory allocation, a 300 percent CPU allocation, 500 GB of NVMe, unlimited transfer, unlimited MySQL databases, cron, and a cap of 200 processes and 30 concurrent web connections per account. CORE-Y is 9 GB and 600 percent for JPY 1,190 a month, CORE-Z 12 GB and 1,200 percent for JPY 2,990. The V2 plans carry a JPY 1,650 setup fee and a 30-day free start. unit GiB; metered on wall-clock; time-boxed-trial |
|---|---|
| Price | none stated |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | not stated |
| Identity | card not published |
| Limits |
The vendor's load-limit page states that accounts carrying load other than web purposes, naming mining and computational processing, are restricted, and the 200-process and 30-connection caps bind before the 6 GB of memory does; the shape is a web host with a large memory allocation, not a virtual machine. |
| Binding | write-gated The vendor's load-limit page states that accounts carrying load other than web purposes, naming mining and computational processing, are restricted, and the 200-process and 30-connection caps bind before the 6 GB of memory does; the shape is a web host with a large memory allocation, not a virtual machine. |
| Interface | unknown inferred from the tooling the provider documents; not probed |
| Tooling | not stated |
| Composes with | For JPY 830 a month with no term, CORE-X offers more memory than any Japanese VPS below JPY 1,600 and a cron scheduler, which is a real shape for a nightly extraction job; it composes with a VPS only where the job is expressed as a web request, because no inbound port can be opened. |
| Reliability | no reliability event recorded |
| Notes | The shape is the interesting part of this record: 6 GB of memory for JPY 830 a month is a quarter of the price of a 4 GB VPS in Japan, and the reason is that it is a shared web host with a large allocation rather than a machine. The constraints are all published, which is unusual: process count, connection count, disk throughput, IOPS and a written restriction on compute workloads. Recorded as qualifies-with-caveat rather than qualifies because no probe of a running job was made and because the vendor's restriction on non-web load is a design constraint on the use. The 30-day free start is stated on the vendor's front page. the card identity cost is inferred from a monthly or hourly billing model, and the signup page is the route that would settle it. |
| Evidence rung | documented |
| Checked | 2026-10-22 (live); stale on 2026-11-21 |
| Parsed numbers |
|
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | www.coreserver.jp/price/ | the price table gives CORE-X at 830円 a month on subscription, 610円 on twelve months and 430円 on thirty-six, CORE-Y at 1,190円 and CORE-Z at 2,990円, with a 1,650円 setup fee on the V2 plans |
| 2026-10-22 | www.coreserver.jp/function/ | the feature table gives CORE-X 500 GB of disk, unlimited transfer, a 6 GB memory allocation and a 300 percent CPU allocation, CORE-Y 700 GB with 9 GB and 600 percent, and CORE-Z 1,000 GB with 12 GB and 1,200 percent, all with cron and unlimited databases |
| 2026-10-22 | help.coreserver.jp/faq/load-limit/ | the vendor's load-limit page gives CORE-X 200 MB/s disk, 2,048 IO operations a second, 30 concurrent web connections and 200 processes per account, rising to 800 processes on CORE-Z, and states that accounts putting load on the server for non-web purposes such as mining or computational processing will be restricted |
More fields (1)
{
"wave2": {
"class": "shared-compute",
"free_tier_kind": "time-boxed-trial",
"shape": {
"vcpu": null,
"ram_gib": 6,
"gpu_class": null,
"gpu_count": 0
}
}
}Unknown or withheld values (10)
$.egress.meteredegress-unknown$.egress.termsnot-stated$.identity_cost.detailprocess$.interfaceinterface-unknown$.per_object_cap.notesprocess$.per_object_cap.statednot-applicable$.reliability_notenone-observed$.retention.notesprocess$.retention.statednot-applicable$.toolingnot-stated