Launch diagnosis
From ¥500For reviewing domains, certificates, access paths, existing hosting, and material risks before migration or purchasing decisions.
- Public path review
- Infrastructure inventory
- Material risk summary
- Recommended sequence
Pricing
Pricing
Cost, capacity, and ongoing responsibility should be clear before implementation.
Page prices indicate the smallest useful engagement, not a universal package. A formal quote separates one-time delivery, recurring maintenance, and third-party resources while stating capacity assumptions, timing, customer dependencies, and out-of-scope handling.
Standard website delivery
From ¥2,000For deployment, migration, and operating entry points across corporate, organization, and program websites. Page count, language, content management, and legacy systems affect scope.
- Deployment and migration
- Domains and TLS
- Cache and forms
- Acceptance and handover
Managed maintenance
From ¥500 / monthFor teams that need scheduled checks, backup-state review, certificate care, and baseline incident response without an internal operations role.
- Scheduled inspection
- Alerts and health
- Backup status
- Agreed small changes
Content, video, and storage
Scoped by capacityFor object storage, video processing, download delivery, multilingual content management, and growing content operations. Provider resources and implementation are priced separately.
- Capacity and peak estimate
- Access and lifecycle
- Publishing permissions
- Monthly cost visibility
Pricing
Every quote separates
One-time deployment feescope
Monthly maintenance feescope
Third-party cloud resource costscope
Custom development outside scopescope
Pricing
Pricing should make cost and responsibility explainable together
Entry prices indicate the smallest useful engagement, not a universal website cost. Formal quotes consider region, content volume, traffic, migration, content-management behavior, security, and ongoing ownership, with assumptions, capacity, and exclusions written down.
One-time delivery
Usually covers defined implementation after diagnosis: deployment, domains and TLS, cache connection, forms, migration, and launch verification. Customer material, interfaces, and provider approvals affect scheduling.
Ongoing maintenance
Covers only agreed checks, certificates, backup status, health, alert response, and small changes. Response windows, check frequency, and holiday coverage are defined before service begins.
Third-party resources
Servers, CDN, object storage, transcoding, video traffic, mail, and domains are commonly billed by external providers. Ruocent fees and variable provider costs are separated where practical.
New or high-risk work
Membership, payment, complex permissions, large migration, performance projects, security review, incident response, and work beyond agreed capacity need a separate assessment before execution.
Primary pricing variables
VariableWhy it changes effortHow a quote states it
Target regions
Determines placement, network verification, and possible compliance
List primary regions and test scope
Content and traffic
Images, video, downloads, and dynamic requests have different economics
State capacity, monthly traffic, peak, and growth assumptions
Existing systems
Migration, legacy URLs, databases, and integrations add dependencies
List migrated objects, downtime, and owners
Operating responsibility
Check frequency, response, and recovery targets set recurring effort
Define coverage, exclusions, and out-of-scope handling
Why do prices say “from” or “scoped”?
Entry work assumes low complexity. Regions, volume, legacy systems, and responsibility can materially change effort; one fixed number would hide work or reduce delivery.
Is there a fee before a formal quote?
Ordinary discussion and directional review are not automatically paid projects. Access-heavy assessment, formal reports, performance testing, or substantial diagnosis is scoped and priced first.
Who pays the cloud providers?
Customer-owned accounts with direct billing are preferred for control and transparency. Any managed billing arrangement states limits, payment, and exit handling.
Can we begin with a small validation?
Yes. A single site, region, content class, or recovery exercise can produce real evidence before expansion. The validation still has acceptance and stop conditions.
How is cancellation or termination handled?
Settlement follows completed work, incurred provider cost, and the project agreement. Deliverable configuration, content, and data are handed over when payment and security conditions are met.
Does a low-cost launch include maintenance?
One-time launch and ongoing ownership are separate. A launch-only scope states who will handle certificates, backups, alerts, and future changes afterward.
A reliable quote explains what the money buys, which costs can grow with the business, and how change will be reassessed instead of presenting an opaque total.