The RE:NODE panel in Georgian: switching language and what changes

The RE:NODE panel can now be read in Georgian from the login page to the last tab of a server. There is one switch, "EN / ქა", in the sidebar beside the theme toggle and on the login page. Press it and the page changes language at once, without a reload, and the choice is saved on your account so the next sign-in, on any browser, opens in the same language. Everything a customer touches is covered: the server list, the console and its power buttons, files, backups, schedules, databases, the GitHub and deploy tabs, the "Work on this server with AI" bar, the support chat, the shop, billing and invoices, and the account pages. What stays in English is what was never ours to translate - your server's own console output, your file names, the text of messages people write - plus parts of the staff side of the panel, which customers do not see.

This post covers how the switch works in detail, what exactly is translated, what deliberately is not, and why we think a Georgian-language panel matters more than it looks for teams that run servers together.

How to switch the panel to Georgian#

There are two places to do it, and they behave the same way.

1. On the login page, before you sign in, press ქა in the "EN / ქა" control. The login form, the password reset and the two-factor checkpoint switch to Georgian.
2. Once signed in, open the sidebar. The same control sits next to the light and dark theme toggle. Press ქა for Georgian or EN for English.

The change is instant. The panel swaps its text in place, so you stay on the page you were on - halfway through editing a schedule, looking at the console, or in the middle of the shop. Nothing is lost by switching.

If you are signed in, the panel also writes the choice to your account. That is the part that makes it stick: the language is a property of your account, not of one browser tab. Sign in tomorrow from a laptop you have never used and the panel opens in Georgian.

If the panel cannot save the choice to your account (a dropped connection, for instance), it switches the page back to the language it was in. We decided a switch that visibly did not happen is better than one that seems to work and silently reverts on the next load, which is the kind of bug people report as "the language setting does nothing".

How the panel decides which language to show#

Every page request picks a language in a fixed order. Knowing the order explains every case where you might see a language you did not expect.

Only a language the panel actually ships is ever used, and today that means English or Georgian. A browser set to Georgian (ka) on a first visit sees the login page in Georgian without anyone pressing anything. A browser set to Russian or German falls through to English.

The cookie is there for one specific moment: signing out. The login page has no account to ask, so without the cookie somebody who had chosen Georgian would be shown English the second they signed out. The cookie lasts a year and holds nothing but the two-letter code. It is a reading preference and nothing about it is sensitive.

Dates follow the language as well. Relative times such as "3 days ago" and full dates on invoices, backups and the activity log are written with Georgian month names and the ka-GE format when the panel is in Georgian, and switch back with the language.

What is translated#

The short version is every page a customer sees. The longer version, area by area, is below, with the Georgian name you will see in the sidebar so you can find your way if you are reading this in English and helping someone who uses the panel in Georgian.

Inside a server, the tabs are translated too:

Console and power controls

The console page is where most people spend their time, so it got the most care. The power buttons are ჩართვა (Start), გადატვირთვა (Restart), გამორთვა (Stop) and იძულებით გაჩერება (Kill), and the kill confirmation explains in Georgian that forcing a stop can damage data. The status badge reads მუშაობს when the server is running, გამორთულია when it is offline and ინსტალირდება while it installs. The memory, CPU and disk graphs, the hints shown when the console is idle, the Ping and Hops strip and its "Test now" button are all in Georgian. See reading the console for what the output itself means.

Files, SFTP and backups

The file manager's toolbar, upload dialogs, editor, archive actions and error messages are translated, as is the SFTP details card. On the Backups tab, creating, locking, restoring and downloading a backup is all in Georgian, including the warnings - the ones that matter most, such as the confirmation before a restore, are the ones you most want to read in your own language. Our longer notes on the file manager are in SFTP and the file manager and on backups in backups that actually restore.

Schedules, databases, network and startup

The Schedules tab, including the task editor with its console command, backup and power action types, is translated. Cron expressions are not, because they are not words: 0 4 * * * means the same in every language, and our guide to cron expressions applies unchanged. The database slot page, the Network tab for ports, the Startup tab and its variables, the proxy slot, the GitHub tab with the pre-flight check, and the deploy history are all in Georgian.

Shop, billing and invoices

The shop - categories, plan cards, the order dialog, payment methods - and the Finances area with subscriptions, invoices, the wallet and renewals are translated. The currency switcher above the shop's prices has a Georgian label, but the rates, currency codes and symbols are not translated, because they come from the published rates. The panel shows lari at the National Bank of Georgia rate and marks it as approximate; USD stays the base.

The AI bar and Connected AI

The "Work on this server with AI" bar above the console reads იმუშავე ამ სერვერზე AI-ით. The purpose dropdown, the Connect AI button (AI-ს დაკავშირება), the share link help and the warning on links that can control the server are all in Georgian. The OAuth consent page that an assistant opens when you connect it is available in both languages. The Connected AI page in the account area, where you revoke links and disconnect assistants, is translated as well. There is more on the feature itself in connecting Claude to your game server and AI access without leaking secrets.

Support chat

The Chat button in the server header (ჩატი), the floating panel, unread counts, "Seen by", whether support is online and the rating card are translated. This matters more than it seems, because the chat is the one thing a suspended server or a failed install still answers, which is exactly when someone is stressed and least wants to decode English interface text.

Account and security

Profile, two-factor setup and recovery codes, API keys, SSH keys, teams, roles, subusers, the activity log and referrals are translated. Setting up two-factor authentication for the first time is a place where people make mistakes, and losing both the authenticator and the recovery codes means the account cannot be recovered - so reading those screens in your own language is not a cosmetic point. Our walk-through is in two-factor on your panel account.

What stays in English, and why#

Some things are not translated on purpose. Knowing which ones saves confusion.

• Your server's own output. The console shows exactly what the game or the app prints. If Minecraft says Done (4.2s)! or Node says Error: Cannot find module, that is the program speaking, not the panel. We never filter or rewrite console output, in any language.
• Your files and their contents. File names, config keys such as max-players or view-distance, environment variable names and the text inside your files stay as you wrote them.
• Messages people write. In the support chat, the interface is Georgian but each message is shown as it was typed. You can write to us in Georgian or English.
• The prompt copied for an AI assistant. When you press the AI bar's "Server won't start" option, the panel copies a ready-to-paste prompt with the console tail. That prompt is written for the assistant to read, not for you, and is left in English deliberately - the assistant understands it, and the console tail inside it is in whatever language your server logs in anyway. You can still talk to the assistant in Georgian.
• Brand and product names. GitHub, SFTP, MCP, phpMyAdmin, Valkey and the names of games are names, not words.
• Parts of the staff side. The staff area of the panel is partly translated and partly English. Customers do not see it, but if you ever wonder why a screenshot from our side looks half English, that is why.

There is also a safety net. If a single Georgian string is missing somewhere - a new button added before its translation - the panel shows the English word for that one label rather than a broken page or a raw key. A missing translation is a missing word, never a missing page. If you spot one, tell us in a ticket or the chat and we will fix it.

Why a Georgian panel matters for teams#

A hosting panel in English works fine for the person who set the server up. It works less well for everyone else, and on most Georgian teams there is an everyone else.

Think about who actually touches a server over its life. A game community has an owner, a couple of admins who restart things and edit configs, maybe a moderator who only needs the console. A small company has a developer who deployed the app and someone in the office who pays the invoice. A school or club has a teacher and a handful of students. The owner may be comfortable in English. The rest often are not, and the price of that is not inconvenience - it is the admin who does not dare press anything, or presses the wrong thing because "Kill" and "Stop" read alike to someone guessing.

The language is set per account, not per server. That means a mixed team needs no compromise: the owner can keep the panel in English while every subuser they invite reads the same server in Georgian. Permissions do not change with language; a subuser who can only use the console sees only the console, in whichever language they picked.

Three places where this pays off in practice:

1. Delegation. Giving someone console-only access is far easier when they can read what each button does. Fewer messages along the lines of "which one restarts it?"
2. Billing. The person who pays is often not the person who runs the server. Invoices, renewals and the lari estimate in Georgian mean they can pay without a technical person standing behind them.
3. Incidents. When a server crashes, its owner gets a warning on the server page and, after repeated restarts, an automatic ticket. Reading that warning and the support chat in your own language is faster at exactly the moment speed counts.

The public site has been readable in Georgian for a while, under /ka. Until now that meant a Georgian visitor read about the product in Georgian and then signed in to an English panel. That gap is closed.

Switching back, and other questions of mechanics#

Switching back to English is the same switch: press EN. It saves the same way. There is no separate setting buried in account preferences that you also need to change.

Each person on a team has their own language. Changing yours does not change it for anyone else on the server, and an owner cannot force a language on a subuser.

The theme is separate from the language. The light and dark switch sits beside the language switch, and both are remembered independently, so Georgian in dark mode is as available as English in light mode.

Nothing about your servers changes when you switch. No restart, no reinstall, no change to files or variables. It is a reading preference and the server does not know or care which language you read the panel in.

If the page looks half-translated for a second after switching, that is the panel fetching the Georgian text for the parts of the page it had not loaded yet. It settles within a moment. If a label stays empty or English for longer, a hard refresh will load the latest strings; if it is still English after that, it is a missing translation and worth reporting.

Troubleshooting the language switch#

A few situations people may run into, with the cause in each case.

• The login page opens in English although I chose Georgian. You are on a browser that has never seen your choice and is set to a language other than Georgian, or the cookie was cleared. Press ქა on the login page; once you sign in, the account setting takes over.
• The login page opens in Georgian and I did not ask for it. Your browser lists Georgian as its preferred language. Press EN, and the choice is remembered from then on.
• I switched, but it went back on the next page. The save to your account failed and the panel undid the switch rather than pretend it worked. Check your connection and try again. If it keeps happening, contact support.
• A colleague sees English on the same server. Language is per account. They need to press the switch on their own account.
• The console is still in English. The panel around it is Georgian; the lines inside it are your server's own output and are not translated.
• Prices in lari differ slightly from the bank's rate today. The lari figure is converted from USD at the published National Bank of Georgia rate and is marked as approximate - treat it as an estimate, not a quote.

FAQ#

Does switching to Georgian cost anything or change my plan?

No. The language switch is available on every plan and every account, and it changes only the text you read. Your servers, billing and permissions are untouched.

Can I write to support in Georgian?

Yes. The support chat and tickets accept whatever you type. The chat interface itself is translated, and messages are shown exactly as written.

Is the panel available in Russian?

No. The panel ships in English and Georgian. The public website also has a Russian version at /ru, but the panel does not, and a browser set to Russian sees the panel in English.

Will my game server's console be translated?

No, and it should not be. The console shows the game's or app's own output, unchanged. Only the panel's controls around it - buttons, graphs, status and hints - are in Georgian.

Does the language affect AI assistants connected to my server?

Only on your side. The AI bar, the share-link help and the OAuth consent page are in Georgian. What the panel sends to the assistant is the same in either language, and passwords and tokens are withheld either way.

Can I set a different language for each subuser?

Each subuser sets their own language on their own account. The owner does not choose it for them, and changing it never affects anyone else.