Travertine Server HostingTravertine Server Hosting
The 1.7-capable Waterfall fork for legacy networks whose players still log in on 1.7.10, running your BungeeCord plugins on İstanbul hardware.
Choose your Game Server
Select from our wide range of optimized game servers. Each server is configured for maximum performance and comes with DDoS protection.
1. Plan Type
2. Location
3. Choose Plan
Bronze 4GB
Silver 6GB
Gold 8GB
Platinum 10GB
Diamond 12GB
Emerald 16GB
Xtreme 32GB
Which Travertine Plan Is Right for You?
Compare recommended use, plan hardware and monthly prices.
| Plan | Recommended for | Hardware | Monthly price |
|---|---|---|---|
| Bronze 4GB | Legacy network, a few hundred playersMore than enough for small and mid-sized 1.7 to 1.16 networks; most RAM stays idle. | 4 vCore Ryzen 9950X · 4 GB DDR5 6000MHz · 50 GB NVMe SSD Samsung 990 PRO | ₺240.00/mo |
| Silver 6GB | 300–600 players, long plugin listComfortable memory margin when the proxy runs many menu and statistics plugins. | 4 vCore Ryzen 9950X · 6 GB DDR5 6000MHz · 60 GB NVMe SSD Samsung 990 PRO | ₺345.00/mo |
| Gold 8GB | 600–1,000 players, many backendsBalanced choice for larger legacy networks with several PvP and lobby servers. | 4 vCore Ryzen 9950X · 8 GB DDR5 6000MHz · 70 GB NVMe SSD Samsung 990 PRO | ₺440.00/mo |
| Platinum 10GB | ~1,000 players, data-heavy pluginsStill 4 vCores; the extra RAM only matters for plugins that hold a lot of data. | 4 vCore Ryzen 9950X · 10 GB DDR5 6000MHz · 100 GB NVMe SSD Samsung 990 PRO | ₺530.00/mo |
| Diamond 12GB | Rarely needed; unusual plugin loadTravertine seldom touches this much memory; if you are growing, fund a Velocity move. | 4 vCore Ryzen 9950X · 12 GB DDR5 6000MHz · 110 GB NVMe SSD Samsung 990 PRO | ₺617.50/mo |
| Emerald 16GB | 1,000+ players, 6 vCores, pre-migrationExtra cores help with login spikes, but running an archived proxy at this size is risky. | 6 vCore Ryzen 9950X · 16 GB DDR5 6000MHz · 120 GB NVMe SSD Samsung 990 PRO | ₺840.00/mo |
| Xtreme 32GB | Not recommended: migrate to Velocity12 vCores offer capacity, but we advise against running unmaintained software this big. | 12 vCore Ryzen 9950X · 32 GB DDR5 6000MHz · 200 GB NVMe SSD Samsung 990 PRO | ₺1520.00/mo |
Why TheCrewHost for Travertine?
Everything you need to keep a legacy Minecraft network running, with an honest view of where Travertine fits and where it does not.
1.7 protocol at the proxy
Travertine was forked because Waterfall only targeted protocol versions upstream BungeeCord supported; it accepts 1.7.x connections at the proxy so long-time players are not turned away.
Familiar Waterfall configuration
Built directly on Waterfall, Travertine uses the same config.yml and waterfall.yml, so servers, priorities and forced_hosts work exactly the way you already know.
BungeeCord plugin API
Copy the announcement, server-selector and permission plugins your legacy network has used for years into the plugins folder and keep running them on the same API.
BungeeGuard for backends
With ip_forward on, BungeeGuard on the proxy and every backend rejects connections without the shared token, a layer that matters even more on software that no longer gets patches.
Tiny resource footprint
Travertine never loads a world, it only routes connections, so small and mid-sized 1.7 to 1.16 networks leave most of Bronze 4 GB unused.
Backups and SFTP access
config.yml, plugin data and your BungeeGuard token are backed up automatically, and you can bring over your old proxy files with SFTP or the web file manager.
For $6.00 (₺240.00) a month, Travertine server hosting at TheCrewHost gets you the Waterfall fork that adds 1.7.x client support, with full access to config.yml and your plugins. Travertine keeps the BungeeCord plugin API while still accepting players on the 1.7 protocol, which is why old-school PvP and legacy survival communities relied on it. To be straight with you: the project was archived in 2022, its final build dates from June 2021 and stops at the 1.16 line. It makes sense for keeping an existing legacy network alive, not for starting a new one. The proxy itself lives on Ryzen 9 9950X hardware in our İstanbul datacenter, behind free DDoS protection.
What is Travertine, and how does it differ from Waterfall?
Travertine is a proxy the PaperMC team built on top of Waterfall to add support for Minecraft 1.7.x clients. It became a separate project for a simple reason: Waterfall intended to support only the protocol versions that upstream BungeeCord supported, and 1.7 had dropped off that list. Travertine took every Waterfall patch and layered 1.7 protocol support over it.
In day-to-day terms, Travertine behaves like a BungeeCord proxy. It loads BungeeCord plugins, it is configured through config.yml, but it does not bounce a player who shows up on a 1.7.10 client. For legacy PvP communities that wanted 1.7 and 1.8 players on one network, it was the de facto answer for a long time.
Builds for the 1.12 through 1.16 version lines are still listed on PaperMC's download pages. The latest belongs to the 1.16 line and dates from June 2021, and PaperMC marks that version as unsupported.
Who should still be running Travertine?
Only admins keeping an established network with a 1.7.x player base running as it is. The GitHub repository was archived in 2022 and is read-only; because the last build is from June 2021, it contains no fixes for any vulnerability found after that date. It also stops at the 1.16 line, so players on 1.17 or newer cannot connect to it directly.
If you are starting fresh or want to open your network to modern versions, look at Velocity instead. It accepts clients from 1.7.2 through the current release, is actively maintained and offers stronger forwarding, so the 1.7 support that justified Travertine exists there too. The trade-off is that you move from BungeeCord plugins to Velocity plugins.
If you do stay on Travertine, reduce the risk: protect every backend with BungeeGuard, install only the proxy plugins you genuinely need, check your backups regularly, and sketch out a migration plan for the medium term.
How do 1.7 players actually reach your backends?
A common misunderstanding needs clearing up first. Travertine lets a player connect to the proxy using the 1.7 protocol, but it does not translate game content between versions. A player arriving on 1.7.10 must be sent to a backend that also accepts that version.
There are two usual ways to do that. One is running the backend itself on an old version such as 1.7.10 or 1.8 with the bungeecord option enabled in spigot.yml. The other is keeping the backend on a newer release and adding ViaVersion, ViaBackwards and ViaRewind; ViaRewind is the piece that lets players on 1.7 and 1.8 join servers running 1.9 or later.
With the second approach, blocks, items and movement do not line up perfectly across versions, so anti-cheat plugins can raise false flags. On a PvP-focused server, test that thoroughly before opening the doors. Checking which client version most of your players actually use, and picking the backend version to match, keeps the translation layer as thin as possible.
Configuring config.yml and securing backends
Configuration works just as it does on Waterfall: config.yml is the main file and extra options live in waterfall.yml. Add each backend's name and the IP:port from its panel under servers, then use the priorities list under listeners to decide where players land at login. forced_hosts can route a specific hostname straight to one server.
Set ip_forward to true; without it, backends only ever see the proxy's address and offline-mode UUIDs. On the backends, enable the bungeecord option in spigot.yml and turn online-mode off in server.properties. The well-known weakness of this setup is that someone connecting straight to a backend port can attempt to log in under a fake identity. Because this proxy no longer receives updates, be extra careful: if you cannot firewall backend ports so only the proxy reaches them, install BungeeGuard on the proxy and every backend, then confirm that connections without the token are refused.
The default config.yml lists a sample admin named md_5 under groups. Replace it with your own name first, or hand permissions to a dedicated permissions plugin.
How much RAM does Travertine need?
Very little. Travertine does not process worlds, entities or blocks; it accepts connections and relays packets to backends. Legacy 1.7 and 1.8 networks typically run in the range of a few hundred concurrent players, so Bronze 4 GB leaves most of its memory idle in nearly every scenario.
Plugins are what push memory up: lots of server-selector menus, statistics collectors, or large player datasets kept on the proxy. If that sounds like your network, Silver or Gold gives comfortable headroom. On the CPU side, Bronze through Diamond include 4 vCores of Ryzen 9 9950X, Emerald 6 and Xtreme 12, but we would not recommend growing a network past a thousand players on an archived proxy.
That is why the real question when choosing a plan is less about player count and more about where your network is heading. For keeping a small legacy community going, the entry plan does the job. If you expect growth, the money is better spent on a Velocity migration than on a large Travertine plan.
How to Set Up a Travertine Server
- 1
Choose a Travertine plan sized for your network
Most legacy networks peak at a few hundred concurrent players, so Bronze 4 GB is enough; move to Silver only if the proxy carries a long plugin list.
- 2
Decide on a backend version strategy
Choose whether 1.7 players go to backends running 1.7.10 or 1.8 directly, or to a newer version that admits them through ViaRewind, and set up backends accordingly.
- 3
Add your servers to config.yml
List backend names and IP:port addresses under servers, put the lobby first in priorities, and set ip_forward to true.
- 4
Prepare backends for forwarding
Enable the bungeecord option in each spigot.yml, set online-mode to false in server.properties, then install BungeeGuard alongside the proxy and match the token.
- 5
Upload plugins and fix the admin entry
Place your BungeeCord plugins in the plugins folder via SFTP, replace the sample md_5 entry under groups with your own name, and restart the proxy.
- 6
Test with a 1.7.10 and a newer client
Log in on 1.7.10 and on 1.8, hop between servers, and once everything works, point your domain at the proxy IP and announce it to your players.
Frequently Asked Questions
What admins ask most before keeping a 1.7-capable BungeeCord network alive on Travertine.
How much does Travertine server hosting cost?
How much RAM and which plan do I need?
Which Minecraft versions does Travertine support?
Is Travertine still maintained?
Do my BungeeCord plugins work on Travertine?
When will my server be ready?
How do players connect to a Travertine network?
How are my backups handled?
Is my Travertine proxy protected against DDoS attacks?
Can I upgrade to a larger plan later?
İstanbul Location,
Maximum Performance
Our İstanbul datacenter runs on Ryzen 9 hardware, delivering low latency to players in Türkiye and good connectivity to Europe, the Middle East and the Caucasus.
Turkey
İstanbul
Turkey
Explore Our Other Services
Everything your project needs — from game servers to VPS, dedicated servers, web hosting and Discord bot hosting.
Connect with our community of gamers and developers
Get instant support, share experiences, and stay updated with the latest news
