Skip to main content
MicrohostingsGame infrastructure
GamesPlatformPlansLocationsFAQContact
BuildingAdmin preview

Navigate

Microhostings

  1. 00Home→
  2. 01Games↗
  3. 02Platform↗
  4. 03Plans↗
  5. 04Locations↗
  6. 05FAQ↗
  7. 06Contact↗

Platform foundation in progress

Admin preview
MicrohostingsGame infrastructure

A planned game hosting platform for deliberate launches, safer operations, and communities that intend to stay awhile.

Product

Game hostingPlatform previewResource guidance

Games

Certification sequenceMinecraft JavaMinecraft Bedrock

Help

FAQContact and access

Status

Location evidencePreview status

Legal

Privacy boundaryService terms status

© 2026 Microhostings

Foundation phase · public access is not open.

Planned game hosting platform

From first boot to every late-night save.

A game hosting experience is being designed around the moments that matter: choosing well, changing safely, and knowing what to do next.

Explore games↓Preview the control room→

Product foundation in progress

Release path
  1. 01
    Minecraft JavaFirst certification candidate
    Planned
  2. 02
    Minecraft BedrockSecond certification candidate
    Planned
  3. →
    Future catalogCapability-led expansion
    Later

The opening sequence

Start narrow. Learn deeply. Expand with proof.

Each game gets a certification path that covers installation, configuration, lifecycle actions, save safety, and recovery before it can be offered.

01
Planned

First certification candidate

Minecraft Java

The first proving ground for a clear install path, deliberate changes, and recoverable world operations.

Certification focus
  • Version-aware templates
  • Mod-path planning
  • Safe lifecycle checks
View Minecraft Java direction→
02
Planned

Second certification candidate

Minecraft Bedrock

The second certification path, focused on dependable save handling and understandable server configuration.

Certification focus
  • World-save protection
  • Configuration guidance
  • Lifecycle recovery
View Minecraft Bedrock direction→

The operator journey

Every action should answer three questions.

What will happen? What could change? What is the safe next move?

  1. 01 · Prepare

    Launch with context

    Every important choice should explain what it affects before a server is created.
  2. 02 · Operate

    Change with confidence

    Risky actions should show their impact, preserve intent, and create a path back.
  3. 03 · Recover

    Stay oriented under pressure

    When something goes wrong, the next safe action should be visible without guesswork.

Control-room direction

World control, without the control-panel noise.

The composition demonstrates hierarchy and intent. Runtime data, server actions, and account state are deliberately absent from this public preview.

Product preview — not connected to a live server

World overview
MHOverviewConsoleFilesBackupsSettings

Selected world

Example world

Illustrative state

Before you act

Review the intended change

Runtime actions will explain impact and recovery context before they can be confirmed.

Readiness path

  1. 01
    Template checkCompatibility context appears here.
  2. 02
    Allocation planResource intent appears here.
  3. 03
    Health gateVerification context appears here.

Resource guidance

A plan should begin with the workload.

Public pricing is intentionally absent until real operating boundaries are validated. The eventual selector will explain why a resource shape fits.

01

World profile

Start with the game, world shape, and extension needs rather than an arbitrary product tier.

02

Player pattern

Consider how the community gathers, when activity peaks, and which operations need extra headroom.

03

Extension path

Leave room for mods, plugins, saves, and future changes without paying for vague promises.

World

Placement without theater

Location guidance before a region promise.

Availability will be shown only after network paths, capacity, and game-specific operating profiles are validated. No map pin is a promise yet.

Network path
Match placement to where the community connects from.
Capacity
Show only locations with validated room for the selected game.
Certification
Offer a game only where its operating profile has passed review.

Straight answers

What is known today.

The product is early enough that honest boundaries matter more than polished promises. These answers will evolve with verified capability.

01When will Microhostings game hosting open?+

A public launch date has not been announced. The platform is moving through foundation work and game certification before access is offered.

02Why begin with Minecraft Java and Minecraft Bedrock?+

Minecraft Java is the first certification candidate and Minecraft Bedrock follows second. Additional games enter only after the shared lifecycle and safety model is proven.

03Will the platform support modded Minecraft?+

Extension support is part of the Minecraft certification plan. Exact loaders, versions, and migration guidance will be published after they pass compatibility checks.

04Can an existing world be moved to the platform?+

Migration paths are part of the product plan, but no transfer workflow is being promised yet. Supported sources and validation steps will be documented before release.

05How will plans and pricing work?+

Plan names, resource boundaries, and pricing will be published only when capacity and operating costs have been validated. This preview does not present purchasable plans.

Stay close to the build

The access channel opens when there is something real to test.

The public contact and early-access workflow is not live in this bounded preview. Until then, this page is the source of truth for the platform direction.

Return to the game sequence ↑