BETA TEST
Rust Bot
Rust+ raid alerts
Turns Rust+ Smart Alarm triggers into instant raid alerts in your team's Discord.
Discord Bot
Independent Development Studio
NYTREX LABS
Discord automation with a server-first edge.
We build focused bots for communities that need practical tools, clear controls, and a proper feedback loop before public release.
Operator-focusedDiscord-nativeBuilt in public
BETA STATUS:TESTING
Server-first design
Features are shaped around real Discord server workflows, not generic bot menus.
Structured testing
Every beta build needs scenarios, bug reports, and a clear route for requests.
Source-led pages
Project pages are ready to mirror real repo docs, commands, and file structure.
Account foundation
Sign-in is the base for server checks, tester access, and future bot settings.
Rust OperationsMusic SessionsServer WorkflowsRaid AlertsMusic QueuesSlash CommandsTester AccessProject RoadmapRust OperationsMusic SessionsServer WorkflowsRaid AlertsMusic QueuesSlash CommandsTester AccessProject Roadmap
Interface Preview
Discord flows before dashboards.
The first product surface is the server itself: slash commands, channel output, staff controls, and clear feedback. The demo keeps the focus there before a bigger dashboard exists.
- Preview the kind of Discord interactions each project is designed around.
- Use the project pages for command references, setup notes, and known limits.
- The account dashboard becomes useful once it can manage real server settings.
Discord beta demo
Sample only#rust-staff
Rust Bot
Nytrex // Rust Bot
Server check complete: online, high pop, staff alerts enabled.
Demo responses are illustrative. Beta access happens through the Discord.
Projects
Active builds in the lab.
Current projects are kept deliberately focused: useful Discord tools, clear setup paths, and feedback that can directly shape the next build.
Beta Programme
A feedback loop that actually works.
The goal is not to collect random comments. Each tester should know what to try, how to report issues, and how requests move from idea to roadmap.
01
Join a test track
Testers choose a project, share their server type, and get placed into the right Discord channel for that build.
02
Run scenarios
Each build gets practical test prompts: install flow, permissions, daily use, edge cases, and failure states.
03
Report cleanly
Issues need context: what happened, what was expected, steps to reproduce, screenshots, and any useful logs.
04
Vote requests
Feature ideas are grouped and prioritised by impact, frequency, and whether they fit the project goal.
Studio Brief
Built for operators. Tested in public.
Nytrex Labs builds Discord-native automation for communities that need useful controls, practical setup, and a direct route from beta feedback to product decisions.
Current focus
Discord tools for Rust operations and music sessions.
Testing model
Scenarios, reports, request voting, and release notes.
Source path
Project pages can sync from real bot repositories.
Roadmap
From beta to self-serve.
The goal is to move from guided beta testing to a reliable account-based platform where server owners can install, configure, and manage Nytrex bots without needing a manual handoff.
01now
Project Betas
- Rust Bot scenarios
- DJ Bot playback tests
- Install notes
02next
Feedback System
- Bug templates
- Request voting
- Weekly changelog
03next
Dashboard + API
- Discord server checks
- Bot settings
- API keys
04future
Public Plans
- Usage tiers
- Priority support
- Stable docs
FAQ
Questions, answered.
What is Nytrex Labs building?
Nytrex Labs builds focused Discord automation projects for game servers and music communities. The current work is centred on practical bots, structured testing, and the account layer needed to manage them properly.
Which projects are active?
Rust Bot and DJ Bot are the active projects. The roadmap is about making those projects easier to install, test, and manage before expanding the product line.
How does beta testing work?
Testers join a project track in Discord, run specific scenarios, report issues with context, and vote on requests based on real server impact.
Do you deploy the bots for me?
No. Server owners should stay in control of their Discord server. The goal is to provide clear invite links, setup notes, and support while the self-serve dashboard is being built.
What do accounts do right now?
Accounts currently support GitHub and Discord sign-in/linking. Next, they should power tester access, Discord server ownership checks, bot settings, and installation state.
Can project pages be generated from GitHub?
Yes. Once the bot repositories are available, the site can be updated from real README files, command registries, package metadata, config examples, tests, and folder structure.
BETA STATUS:TESTING
Join the project loop.
Get beta access, follow release notes, report issues, and help prioritise the features that make the bots more useful in real servers.