Today we connected several pieces that customers experience as one journey: choosing Hashmedo, creating an account, entering the right hosted workspace, and growing into a larger plan.
Start with the plan that fits
A new customer can already begin with the free Starter plan. Today we built the same direct path for Starter Plus and Pro, including monthly and yearly choices.
The important part is what happens behind the checkout. Hashmedo keeps the commercial decision, account identity, organization creation, and workspace placement as separate verified steps. That makes interrupted signups recoverable and prevents a repeated click or delayed event from creating duplicate accounts or organizations.
Upgrade without starting over
We also strengthened the path for an existing organization to move from Starter to Starter Plus or Pro, and from Starter Plus to Pro.
An upgrade keeps the same organization, people, inventory, history, and hosted workspace. When an existing paid subscription changes, the customer sees the exact adjustment before confirming. Hashmedo then waits for confirmed activation before presenting the new plan as active.
That final distinction matters. A checkout window closing successfully is not the same as a completed entitlement change, especially when payment and service events arrive asynchronously.
Flexible placement, one familiar entrance
Hashmedo Hosted can now direct new registrations for different plans to the appropriate available cell. This gives us room to add capacity and keep plan groups operationally separate without asking customers to understand the underlying hosting layout.
Customers still enter through the same Hashmedo address. Placement remains an operational concern behind the product, not another decision the customer has to make.
Safer releases across cells
We extended our blue-green release process to dynamically created hosted cells. Each cell can prepare and verify a new version while the current version keeps serving users, then switch traffic only when the candidate is healthy.
The application and its background work now move together, and verification uses the same route through which customers reach the service. This reduces deployment interruption and makes release status a more faithful picture of what is actually running.
Clearer account setup
Password screens now explain the active requirements before a person submits the form. The guidance comes from the same identity policy that performs the validation, so it stays accurate when the policy changes.
We verified the experience across desktop and mobile layouts and all six languages supported by Hashmedo.
Why this matters
Pricing, identity, organization setup, hosted placement, and deployment can look like separate engineering systems. To a customer, they form one promise: start without confusion, keep the work you have already done, and receive the plan you selected reliably.
Today’s progress makes that promise more concrete. The next step is full sandbox acceptance of both new paid journeys—including checkout, registration, provisioning, routing, and first workspace access—before we treat them as ready for launch.