Credits that actually help you ship: Welcome, Team, MVP, Migration

We’re introducing four promo-credit packages that are useful (you can do real work), predictable (clear expiry and guardrails), and aligned with production use—not just “hello world.” Credits are applied hourly and never exceed the monthly cap of the plan you run.

Why credits at all?

Because real evaluation needs real workloads: CI jobs, staging environments, data imports, soak tests, or a safe window to run old and new stacks in parallel. Our credits are designed to cover exactly that - without surprise bills.

Packages at a glance

Credits are a pool: they apply to hourly charges across the period and expire at the end if unused.

Package details

1) Welcome package — €15 for 14 days (email only)

• What you can do: spin up our €5/month entry VM, try a larger shape briefly, test SSH access, images, backups, and network.
• Why it exists: a quick, no-friction taste of our cloud and control panel.
• After 14 days: credits expire; we provide a short grace window (72 hours) to top up your account and keep any running servers. If there’s no top-up, servers are deleted (backups follow the standard retention).

2) Team package — €100 for 1 month (corp email + ticket)

• Use cases: run staging and preview environments, integrate CI/CD (builds, integration tests), exercise your monitoring/alerts, try GitOps rollouts.
• Why we ask for a ticket: so we understand your stack and help you choose shapes, storage, and alerting from day one (fewer surprises, faster results).

3) MVP package — €300 for 3 months (corp email + ticket + quick call)

• Use cases: launch an MVP with real users, run AB tests/feature flags, do soak testing and performance drills, and stabilize your observability (dashboards, alerts, backups/restore drills).
• Why the call: a 15–20 min check aligns expectations (traffic profile, peaks, rollback plan, backup policy). We tailor guidance so you don’t burn credits on the wrong shape.

4) Migration package — €1000 for 6 months (qualified migrations)

• Use cases: parallel run (old vs new), data sync/backfill, staged cutovers, gradual traffic shifts, capacity rehearsals, and post-cutover hardening.
• Why 6 months: real migrations take calendar time—budget cycles, dependencies, and validation in production. The window lets you move without pressure.
• How to apply: file a migration ticket with a brief outline (current footprint, target region, timeline). We’ll pair you with an engineer and approve credits tied to that plan.

How credits work (the fine print, made simple)

• Hourly billing with a monthly cap. You’re billed per hour; the plan’s monthly price is the maximum for a full month (730 h).
• Deduction order: ServersCamp Credits → account balance → saved payment method / invoice.
• Expiry: credits expire at the end of the package window. Unused portions do not roll over.
• Grace window on expiry: we keep your servers for up to 72 hours to let you add funds; after that, servers are deleted (backups follow the normal retention policy).
• Scope: credits apply to compute and standard storage. Pass-through items (e.g., extra IPv4, certain third-party fees) may not be covered.
• Fair Use: traffic is unmetered (FUP)—we don’t bill per-GB, but we protect overall network quality.
• Abuse policy: no crypto mining, spam/proxies, or illegal content. We may rate-limit or suspend abusive use to protect other tenants.
• Non-cash: credits are non-withdrawable, non-transferable, non-refundable and may require verification (as above).

Why this is good for engineering teams

• Realistic runway. CI jobs, staging, migrations, and early user traffic are exactly what credits cover.
• Production-minded defaults. Daily backups (7 days), unmetered traffic (FUP), predictable scaling.
• Help when it matters. For Team/MVP/Migration packages, our engineers review your use case and recommend shapes, storage, and alerting—so time goes into shipping, not yak-shaving.

How to claim

• Welcome: sign up with email → credits apply automatically.
• Team: sign up with company domain email → open a support ticket “Team package request.”
• MVP: same as Team + pick a time for a quick verification call.
• Migration: open a migration ticket with a short outline; we’ll schedule an engineer call and approve the package.

Ready to proceed?

Sign up in the control panel here: Create your account