Servury deploys in 30 seconds with no email — anyone kept one past a month?

Spun up a Servury box on Sunday to see whether the thirty-second claim is real. It is — coin in, SSH key back, no email, no account, no form. Under a minute end to end.

Which is the part that makes me want to hear from someone six months in rather than six days. IME the interesting question about a host with no signup is never provisioning, it is what the second month looks like. No email means no invoice reminder, no password reset and no way to prove the box is yours.

What I have so far is the same nag I run against everything else:

#!/bin/sh
# expiry-nag — daily, from a machine unrelated to the box
set -eu
days=$(( ( $(cat "$EXPIRY_EPOCH") - $(date +%s) ) / 86400 ))
[ "$days" -le 7 ] && logger -t expiry-nag "$BOX expires in ${days}d"
exit 0

Anyone actually kept one alive past a month? What bit you the first time?

Four month on one box. Is fine, no downtime I notice.

Anyway no email mean no password reset, remember this. I write the deploy token in two place before I even SSH first time, because if you lose it nobody help you. Is not like other host where you cry to support and they fix.

how do you even find the box again

The no-email property is a data minimisation property and people consistently over-read it.

It helps at the moment someone asks the provider what they hold. It does nothing at the moment someone asks the datacentre for the disk, and since the locations are described as "multiple" rather than named, you do not know which datacentre that is or which country's process applies to it. That is a strange thing to accept from a host you chose for privacy reasons.

Ask them where the box is before you put anything on it. If the answer is vague, that is the answer.

I have had two there since spring and I would point people at it for a specific job rather than as a general recommendation, which is roughly how I feel about the whole fast-provision tier.

The job it is good at: four dollars a month, no email, no account, coin or cash in the post, and a box that exists ninety seconds after you decide you want one. For throwaway infrastructure — a redirect node, a scratch box, something you intend to burn in a fortnight — that is close to ideal and nothing mainstream competes.

The caveats are real and there are two. First, it is a newer shop without much of a track record, so do not put the thing you cannot rebuild on it; I would not have said that about a host with ten years behind them. Second, they take cards through a normal card processor alongside the coins, which is fine in itself but means the "no personal info" line describes the crypto path only, and plenty of people will click the easy button and undo the entire point.

Depends what you're running. Disposable: yes, easily. Load-bearing: not yet.

A card processor on a no-KYC host. Somebody explain that one to me.

Because most of their customers are not us. Offering a card lane costs them nothing and doubles the addressable market; the coin lane is still there and still behaves as advertised. It only becomes a contradiction if you assume the shop was built for this board.

Worth separating two things that keep getting welded together in these threads, because Servury is a clean example of the difference and people are about to learn it the expensive way.

Fast provisioning is an operational property

Ninety seconds to a box changes how you design, not how exposed you are. It means infrastructure becomes disposable: you stop repairing things and start replacing them, you stop caring about a box's history, and the correct response to almost any incident becomes "burn it and rebuild". That is genuinely valuable and it is available from plenty of hosts who will also cheerfully take your passport.

The corollary nobody plans for is that disposable infrastructure requires a rebuild script that actually works, tested, in a repo that is not on the box. Without that you have not bought disposability, you have bought a faster way to lose things.

No account is a privacy property with an operational cost

The cost is recovery. There is no password reset, no billing history to point at, no agent who can be persuaded that you are you, because from their side there is no you. If you lose the key material, the box is gone and there is no argument available to you. That is the same trade the API-only hosts make and it is a fine trade, but it has to be a decision rather than a surprise.

Where I would put the line

Under a month of intended life and nothing on it you would miss: excellent, and four dollars is not a typo. Over three months, or anything with state that matters: I want a provider whose worst week I have already read about somewhere, and a newer shop by definition has not had one in public yet. That is not a criticism of Servury, it is a criticism of buying anything important from anyone with a short public record.

I have not tested their cash-by-mail path, so I cannot tell you whether it behaves as well as the coin path.

Summary: brilliant for things you plan to throw away, and the plan to throw them away is not optional.

four dollars. just buy one and stop reading

Three weeks in, closing this out.

Box is still up, renewal was a second coin payment against the same identifier and took about as long as the first one. Asked where the box actually sits and got a straight answer naming the country, which addresses nullroute's point better than I expected — it is not published, but they will tell you if you ask before you buy.

Running it as byte_broker and hexforge described: a redirect node I could lose tomorrow without caring, rebuild script in a repo elsewhere, nothing with state on it. In that role it does the job and the price is close to absurd. Marking solved, with the caveat that "solved" here means "solved for disposable boxes".