• @Di7design @royendo, we probably should list the $0.15/Compute unit/hr somewhere on the left side of the page. We already list the storage rate ($1/GB/mo above 1GB).
• Reset to my usage button should be disabled if the numbers reflect current configuration
• Maybe "reset to my usage' should be "Reset to current configuration"
• Development has a label called "optional" which i don't think makes sense.
• Rename "Hours per day" to "Active hours per day" with a tooltip that reads "We hibernate your deployment when it’s inactive, saving you on cost."
• Subscribe to Pro should take you to the Stripe Checkout page not the Stripe billing portal
• The First Bill label makes sense if you are viewing this cost estimator on a Trial plan or Team plan. It's probably not the right copy for a Pro plan user

set to draft while DI redesigns; we may not need this page in product if we have on marketing page; reroute there instead

• Split the left panel into two sections: Compute and Storage. Today the panel title Select compute unit doesn't cover Storage, and the $0.15/unit/hr hint sitting next to it could read as applying to storage. With a Compute subsection (showing $0.15/unit/hr once in its header) and a Storage subsection (showing $1/GB/mo above 1 GB free in its header), each rate has one obvious home. Drop the per-row rate descriptions: Minimum 2 units · $0.15/unit/hr on Production becomes Minimum 2 units, and Same rate as prod unit on Development drops entirely.
• Formulas need units. 4 units × 24 hrs × 30 days × $0.15 → 4 units × 24 hrs/day × 30 days × $0.15/unit/hr.

1. We should just rename the header to compute and storage (same as ClickHouse), there is no necessity to separate them into 2 sections.
2. Adding full units in every formula makes it harder to scan and feels redundant since the context is already defined on the left. We could keep the formulas lighter for readability and show the detailed pricing on the top section to make it clear before user play around the numbers.

See updated design here. @ericokuma Would like you to review first before Roy change it.

Major changes:

1. Move the reset button inside the number configuration section. (I don't like the long action name as reset to current configuration; make the button too long. It should be simple and intuitive enough that reset will reset to current usage.(Reset to 0 doesn’t make any sense anyway.)
2. Remove tooltip for Production's active hours per day
3. make hour selector the same row with each unit selector
4. add always on checkbox for 24h running.

Additional Q for @royendo :

1. Can we cap the hour input at 24? If a user type a number over 24, we should just clamp it to 24. Right now, I briefly see invalid values and the pricing updates in real time, which feels off.
2. Any plan to allow user to config active hours not just by numbers, but by time windows? Like only run day time, or from 9-5 etc.
3. Do we have a maximum storage size limit? I noticed that CH’s maximum data volume is 1TB. Should we set a similar limit for our storage? If the storage is unlimited, we can allow users to select a unit of measurement. Additionally, if we can, we can automatically convert the unit to TB when the user inputs 1000GB and the number becomes 1.

Thanks Di! What happens when a user clicks on Always on? Does the hours per day switch to 24 and grays out? What happens if they uncheck always on?

If always on checked, the stepper should switch number to 24, but not disabled, if user input other numbers, uncheck the checkbox. (We can have a muted state for the stepper when always on checked.

Thanks Di! What happens when a user clicks on Always on? Does the hours per day switch to 24 and grays out? What happens if they uncheck always on?

Would it be better to use a slider instead then? So it's faster to slide around and we don't need to worry about the always on checkbox?

Ah i see that clickhouse uses an always on checkbox. When you click on it, it moves their slider to 24 and grays out the slider but you can move the slider still and it will get out of disabled state. If you uncheck the always on checkbox, it goes back to the original number it was on prior to enabling always on

all the other changes looks good to me!

Would it be better to use a slider instead then? So it's faster to slide around and we don't need to worry about the always on checkbox?

Good call-out, I did try sliders and moved away from them for a few reasons:

1. The unit selectors above are already steppers. Mixing steppers + sliders for the same "pick a small number" pattern makes the form feel less consistent.
2. Sliders are great for continuous or exploratory values, but for a small discrete range (1–24 integers) people usually know the exact number they want. Steppers (or typing) get you there faster than a draggy slider.
3. Two sliders stacked visually dominate the left column and pull focus away from the estimate + CTA on the right.
   The "Always on" checkbox already covers the 24-hour edge case, so the stepper only needs to serve the common 1–23 range.
4. The whole form is only 5 number inputs, it should stay a simple, consistent pattern that lets people type or step to the value fast. Adding sliders breaks the stepper pattern we're already using for units, and for a small integer range (1–24) a slider is actually slower and less precise than +/− or typing.(CH's form has different input formats for each variable, which I think is very bad form design and hard to read.)

Happy to revisit if we see people struggle in usability testing, but I'd want to keep the form pattern-consistent first.

okay makes sense!

Weird @royendo, i'm trying to test this but not seeing the feature

removed all extra pages from PR, you need to manually go the URL; when doing QA, you can ask Claude how to test the PR

http://localhost:3000/{org_id}/-/settings/billing/estimate