Frequently asked questions

No — it's a one-week trial with 100MB of memory, no credit card required. Our free trial is meant to let you try the real thing before deciding, not to run production workloads on indefinitely for free.

No, not for the free trial. Payment details are only needed if you upgrade to a paid plan.

The free instance and its data are deleted at the end of the one-week trial. You can start another free instance afterward — only one active free instance is allowed per account at a time. This limit doesn't apply to paid instances: you can run paid instances alongside a free one, or without one at all, at any time.

Paid plans are prorated by the minute against the plan's monthly price — you're only charged for the time an instance was actually running, with no rounding up to the next hour. For example, an instance on the 130 €/month plan, run for 6h 15m (375 minutes), would cost around 1.12 € (that is, 375 min × (130 € / (30 × 24 × 60))).

You can cancel anytime; you're not locked into a monthly commitment. Prices shown exclude VAT.

Not currently — egress is free on all plans today. Velstash reserves the right to introduce usage-based pricing for disproportionately high external traffic in the future, with advance notice, but this isn't currently in effect.

EU consumer law gives a 14-day right to cancel most online purchases. However, since Velstash starts provisioning your instance immediately on payment, checkout asks you to confirm the Service to begin immediately after it is requested, and to expressly accept that you lose your right to withdrawal.

Doing so means that you accept to be charged proportionally for the time the Service was actually active since it was provisioned, per Section 4 of the Terms of Service. You can still cancel the service anytime. See the full Terms of Service for details.

Dramatically cheaper — see the pricing page for a comparison against GCP Memorystore, including the per-GiB math behind the claim.

1MB by default. Items over that limit fail silently on set, so check the result code or error your client returns if a value doesn't seem to be sticking.

No — it's set once at creation and used to compute per-prefix statistics in the dashboard. Choose it deliberately before you go live.

Yes, on a separate port (11212) from the plain connection (11211). Native support depends on your language's client library — some connect directly, while others (like PHP's ext-memcached) need a local TLS-terminating proxy like stunnel. See the connecting guide for your language.

Yes — you can create additional scoped credentials with different permissions, such as a read-only credential for a reporting service, or one without flush access for anything that shouldn't be able to wipe the cache.

Passwords are shown once at creation and can't be retrieved afterward, but you can generate a new set of credentials anytime from the instance's detail page.

Cache instances can be hosted in the region you choose — currently Europe (OVH, Gravelines, France), with more planned. Velstash's own infrastructure (the website, dashboard, and account data) stays in the EU regardless of which region you pick for your instance.

Yes — see the DPA page, relevant if you need one for GDPR compliance.

Authentication runs through a lightweight proxy in front of memcached: the first command on each connection is a set carrying your username and password, which the proxy checks before allowing further commands.

This is standard Memcached authentication and doesn't require SASL support, which not every client or hosting environment has properly compiled in. See the connecting guide for your language for details.

You get a dedicated cache instance reachable over the network, with credentials scoped to you and monitoring, alerting, and credential scoping built into the dashboard — no server, monitoring, firewall or configuration to maintain yourself.

We don't pay retail cloud prices: instead, we leverage bare-metal infrastructure and/or long-term capacity commitments to secure the best price for our clients, without cutting corners on reliability. See the pricing page for a detailed comparison against GCP Memorystore.