Run multiple Nighty accounts

One Nighty service runs one Discord account. If you want to run three accounts, you need three Nighty instances, and the tidy way to do that is to put them inside a Fleet: you buy one pool of CPU, memory and storage, then deploy as many Nighty instances into it as it has room for.

This guide covers how that works, how to size the pool, and how to move a Nighty you already have into a fleet.

Why one service is one account

Everything Nighty remembers, its license, your Discord login, the bot token, the Web UI credentials, your themes and scripts, lives in that service's own volume:

prefix/drive_c/users/nighty/AppData/Roaming/Nighty Selfbot/

One volume, one Nighty install, one set of credentials. There is no "add another account" switch inside Nighty on our platform, so a second account always means a second Nighty instance with its own volume, its own Web UI, and its own copy of Nighty.exe.

Standalone orders vs a fleet

You can run several Nighty instances either way. The difference is how they're billed and managed, not what they can do.

	Separate standalone orders	One fleet
Orders and invoices	One per account	One, for the fleet
Renewal dates	One per account	One
Adding another account	New order, new invoice, new checkout	Deployed instantly from the pool, no invoice
Storage floor	5 GB minimum per order	No per-instance floor, only your actual disk usage
Resizing	Per order	Per instance, freely, within the pool
Add-ons	Per order	Bought once on the fleet, shared
Where you see them	Separate entries in your order list	One fleet workspace

A fleet is not a discount

CPU, memory and storage cost the same per unit whether you buy them as a fleet or as standalone Nighty plans. What a fleet buys you is one invoice instead of several, and the ability to spin up account number four in about a minute without going through checkout again.

Step 1: work out how big the pool needs to be

The standalone Nighty plans are the best sizing reference for what one account needs:

Plan	CPU	Memory	Storage	Good for
Starter	1 vCPU	3 GB	5 GB	One account, light use
Standard	2 vCPU	4 GB	10 GB	Scripts and integrations
Pro	4 vCPU	8 GB	15 GB	Heavy automation

Add up one row per account you plan to run. Three fairly light accounts is roughly 3 vCPU, 9 GB memory, 15 GB storage.

A fleet has its own floor of 2 vCPU, 4 GB memory and 15 GB storage, so it only starts making sense at around two accounts and up. For a single account, order Nighty standalone.

Leave a little headroom

A new instance can only be deployed if its CPU, memory and storage all still fit in what's left of the pool. Sizing the fleet exactly to the sum of your instances means the next one won't fit at all. An extra vCPU and a few GB saves you a fleet resize later.

Step 2: order the fleet

In the dashboard, go to Store, pick Fleet, and set the CPU, memory and storage you worked out above. Choose your region here: every instance you deploy into the fleet inherits it, so pick the one closest to you.

Longer billing terms carry a discount, which is applied to the fleet order as a whole. The discount is shown on the checkout screen.

Step 3: deploy a Nighty instance into the fleet

Open the fleet, then in the Servers section click Add server. You'll land on a store view scoped to that fleet, headed "Choose what to deploy inside …". Nighty is under Bots & Voice.

From there:

1. Resources. Set CPU, memory and storage for this one instance. It's deducted from the fleet pool, and the form tells you the ceiling you have left.
2. Web UI credentials. Pick a username and a password (at least 8 characters). These are per instance, so each account gets its own login. Don't reuse one password across all of them.
3. Deploy server. There's no region step (it's inherited) and no invoice. The instance is provisioned immediately from the fleet's resources.

Step 4: bring the instance online

Each instance is set up on its own, exactly like a standalone Nighty:

1. Open the instance, go to the Files tab, and upload your Nighty.exe into the root folder. It's picked up automatically and Nighty starts.
2. Wait 30 to 90 seconds for it to boot. The Console tab shows progress.
3. Open the Web UI URL shown on the instance's page. Every instance gets its own HTTPS address.
4. In Nighty's own 4-step flow: accept the license, log in with the Discord account for this instance, enter the bot token, and authorize via OAuth.

Then repeat steps 3 and 4 for each additional account.

One Discord account per instance

Log each instance into a different Discord account. Two instances signed into the same account will fight over the same session. Whether your Nighty license covers more than one account is between you and Nighty, we don't manage or supply licenses.

Moving an existing Nighty into a fleet

If you already run a standalone Nighty and want it in the pool with the rest, you don't have to rebuild it. Open the order, find Move Into Fleet, choose the target fleet and confirm with Move service. The service and its data move into the fleet workspace, and future billing comes from the fleet instead.

The move is refused unless all of these hold:

• The fleet is active and has room for the service's current CPU, memory and storage.
• The Nighty order is active or suspended, and isn't already in a fleet.
• It isn't running as a free trial. Trials have to convert to a paid order first.
• It has no active add-ons. Add-ons belong on the fleet, not on individual servers inside it.
• It has no pending invoice and no resize in progress.

Living with the pool

• Fleet resources at the top of the workspace shows what's allocated across your instances, with live usage in colour. Allocated is what you're paying for; live is what Nighty is actually using.
• Edit resources on an instance re-allocates within the fleet. Fleet members have no 5 GB storage floor, but you still can't shrink storage below what's on disk right now, and shrinking storage briefly stops the instance.
• Remove from Fleet cancels and terminates that instance immediately and deletes its data, including its Nighty login and license state. It is not reversible, so back up the volume first if you might want it back.

Frequently asked questions

Can one instance run two Discord accounts?

No. Nighty keeps one account's license, token and settings in one Wine prefix on one volume. Two accounts means two instances.

Do I need a separate copy of Nighty.exe for each instance?

You need to upload Nighty.exe into each instance's volume, yes, since each has its own filesystem. We don't ship the binary. How many accounts your Nighty license covers is Nighty's rule, not ours.

Does the Nighty free trial work inside a fleet?

No. The trial applies to a standalone Nighty order. Instances deployed inside a fleet are paid for out of the pool you already bought, and a trial order can't be moved into a fleet until it converts to a paid one.

Is running four accounts in a fleet cheaper than four standalone orders?

Not per unit of CPU, memory or storage, those are priced the same either way. You save on the storage floor (5 GB minimum per standalone order, none inside a fleet), you get one invoice and one renewal date instead of four, and add-ons are bought once on the fleet rather than per server.

What happens if I try to deploy an instance that doesn't fit?

The order is rejected with a quota error. Resize the fleet to add capacity, then deploy again. Cancelled and terminated instances don't count against the pool.

Can I put a fleet inside another fleet?

No, fleets don't nest. A fleet only holds regular services.

Do instances in a fleet share files or see each other?

No. Each instance gets its own volume and its own Web UI address. They share the resource pool and the region, nothing else.