Whether Offshore or Surface, we have it all, a lot of Server
options for various types of use!
Main sales at Impreza Host,
get the solution that works for you
Impreza Infrastructure
Owned and operated by us
Our own hypervisors in ten countries
Most offshore hosts resell slices of somebody else’s cloud. That means somebody else holds your disk, your logs and your payment record. Impreza runs its own virtualization hosts in Ukraine, Romania, Iceland, the Netherlands, the United States, Russia, Switzerland, Hong Kong, Lithuania and Finland. Your VM boots on a server we control end to end, from the hypervisor down.
Every server we sell, VPS or dedicated, in every location we list, runs on infrastructure we operate ourselves. There is no reseller layer between you and the machine.
What runs on servers we operate ourselves
- The hypervisors that run customer VMs, in ten countries
- Object storage for customer data and for our own backups
- Dedicated backup servers, kept apart from the hypervisors
- The crypto payment gateways: Bitcoin, Monero, USDT and TRX settle on our nodes
- The code repository, the secrets vault and the staff access gateway
- Monitoring, intrusion detection and security logging
- The Tor mirrors of the client portal and of our support chat
Everything on that list is administered by our team, on servers we operate exclusively. See how a dedicated server or an offshore VPS fits into it.
Data Protection
Backups on servers we run
Customer VMs are backed up daily to our own dedicated backup servers, which are physically separate from the hypervisors that run them. Backups never sit in a third-party cloud account. We test the full cycle, write, verify, restore and boot, before we trust a backup target. Our object storage runs on our own hardware in Finland with 120 TB of capacity, and the same storage is available to you as S3-compatible object storage.
Snapshots and scheduled backups, self-service
On a VPS you can take a snapshot before a risky change and roll back in one step, create backups on demand, and set a backup schedule. All of it is available from the panel, from the API and from an AI agent connected through our MCP server. On a dedicated server the disks are yours alone, and our backup storage is available to receive your copies.
Jurisdictions and network
Your contract with Impreza is governed by the law of the Seychelles. The hardware, however, obeys the law of the country it stands in. That is why we let you choose the location per project instead of per account, and why we publish a jurisdiction guide that says plainly what each country means for your data.
What we publish, and what we do not
- We publish the countries where we run our own hypervisors, what is ours and what is not, and the policies that apply to your data.
- We do not publish IP ranges, hostnames, node names, capacity or network details. A public map of our fleet would hand a target to anyone who wants to attack it or correlate it, and our customers’ anonymity depends on us not doing that.
Where the hardware lives
We choose a location for its jurisdiction first and for the facility second. Every one of the ten countries above hosts servers that only our team administers.
Network
Each location has its own upstream connectivity, so a problem in one country does not touch another. Every location can serve Tor: any VM or app can be published as a .onion address, and our own portal is reachable over Tor as well. See how to publish a .onion site.
Security
Physical security is the facility layer: staffed sites, cameras and access control. Everything from the server up is ours: no reseller panel, and nobody outside our team with a login to your hypervisor.
DMCA and takedowns
“DMCA ignored” describes our policy: we do not act on automated takedown notices. It is not immunity from the courts. A valid order from the country where a server stands has to be treated as such, which is exactly why the choice of country is yours.
Court orders and logs
We keep as little as we can. Connection and access logs are retained for a maximum of seven days, and we do not keep what we do not need. The details are in our privacy policy.
Abuse
What we do refuse is written in the acceptable use policy: malware, intrusion, spam and abuse material involving minors. Everything else is your business.
Why this matters: chain of custody
Fewer hands on your data
A resold server has at least two owners: the brand you paid and the company that actually holds the disk. A payment through a processor adds a third. Each one keeps records, answers to a different jurisdiction and can be compelled without you ever hearing about it. Every hand we remove from that chain is a hand that cannot talk.
Payments without a middleman
Bitcoin, Monero, USDT and TRX go from your wallet to nodes we run ourselves, confirmed on chain, with nobody in between asking who you are. Details on the pay with crypto page.
Not a white label
This page used to describe a “white labeled architecture” of resold servers. That text came with a reseller template and it was never how Impreza works. We are not a brand on top of someone else’s panel: the hypervisors, the storage, the backups and the payment rails listed above are ours, and every server we sell runs on them.
Hosting Security
Security here is a set of things we actually run, not a list of adjectives. Below is what protects your server and your account, layer by layer, written so that you can check it against what you see.
Security goals
Privacy
You can open an account with no identity documents and no email address. The client portal carries no third-party analytics or trackers. Logs live seven days at most.
Integrity
Every administrative action on our fleet is tied to a named person and a recorded session. There are no shared passwords and no anonymous root logins.
Data protection
Backups are taken to separate servers we run, and we test restores before we trust a target.
Identification
Your account is an Account ID plus a one-time recovery code, shown once when you sign up. We never ask who you are. Read about the no-email signup.
Network protection
Every host starts from a default-deny firewall and opens only what it serves. Intrusion detection feeds a central security log that our team reviews.
How we run security, in seven layers
Our security model combines the systems we operate1, the procedures our team follows2 and the audits we run on ourselves3. The seven layers below say what each one does in practice.
Layer 1: jurisdiction and facility
We pick countries for their legal posture toward privacy and hosting, and datacenters for stable power, connectivity and physical access control. We do not name the facilities, for the reason given above.
The ten countries above are where our own hypervisors run VPS. Dedicated servers in every location we list are ours as well: no reseller and no partner in between. When a location cannot meet the bar, we do not offer it.
Layer 2: network
Our public web properties sit behind an edge that absorbs volumetric attacks and hides the origin servers. Customer servers are reachable directly, as they should be, and are protected at the host.
Firewall by default
Every server we operate starts closed and opens only the ports it serves. Administrative access does not go through a port open to the internet; it goes through our own gateway.
Intrusion detection
Network and host sensors send their alerts to a security log we run ourselves, not to a SaaS. Repeated attackers are blocked automatically.
DDoS mitigation
Where we sell DDoS-protected servers, the network edge in that location absorbs volumetric attacks before they reach your machine. If your project attracts that kind of attention, tell us before you order and we will point you to the right location.
Layer 3: hosts
Host monitoring and security logging
Every server in our fleet reports to our own monitoring and to our own security log: resource health, configuration baselines, file changes, logins and failed logins. Alerts reach the team in minutes and are checked by a person.
Hardware and virtualization
Customer VMs run on KVM, on server hardware under our exclusive control. Hypervisors are ours to patch, to configure and to inspect. Windows Server is available alongside Linux on our VDS plans.
Layer 4: software and updates
The fleet runs Linux. We keep the surface small and we keep it current.
Security updates
Security updates are applied automatically on our own servers. Anything that touches a customer’s running service is scheduled and announced instead of pushed silently.
Vulnerability scanning
Our hosts are checked continuously against current vulnerability databases, and the results are part of the same security log our team reviews.
Change control
Changes to firewalls, backups and access are backed up before they are made and verified from the outside afterwards. We write down what changed and how it was checked.
Layer 5: our own platform
The parts that touch your identity and your money are built and run by us: the signup flow, the API, the MCP server and the crypto payment gateways. Nothing about who you are passes through a third-party service on its way to us.
The software behind the platform runs on our servers, behind our own access gateway, never as someone else’s hosted service. Secrets live in a self-hosted vault, never in shared files.
Layer 6: people and access
The weakest link in any security chain is the people who hold the keys. We keep that circle small and accountable: staff reach servers through our own access gateway, scoped per server and per person, with every session recorded.
There are no shared passwords and no anonymous root logins. Access is granted for a task and removed when the task is done. When someone leaves, their access leaves with them, and we check that it did.
Layer 7: audit
Audit is what keeps the other six layers honest. We periodically re-check who holds which keys, whether every host still reports to monitoring and security logging, whether backups ran and can be restored, and whether firewalls still match what we wrote down.
When an audit finds something wrong, we treat it as an incident, fix it, and record what we learned so it does not repeat. If you want to know how we handle a specific risk, ask support. We would rather answer than impress.
Questions? Problems? Contact Us!
Any questions or problems with your Cloud Hosting service, please contact us, our support is online 24×7!
TAGS
Still have questions? Contact us anytime, or send us a Ticket!