Why I’m Thinking About Building an Open-Source Panel to Fix the Mess

[benjyteve]

It’s common to see complaints about certain panels regarding their lack of security, problems, bugs, etc. While many people might use the “official” versions or mods, patches, etc., the outcome is the same: service owners end up dealing with issues, spending a lot of money on maintenance, and ultimately facing a high risk of being detected or getting hacked along the way.

Over the years, there have been many leaks of source codes and services exposed to authorities, and they all had one thing in common: a panel that many idolized but in most cases ended up being a disappointment (I’ll avoid naming it because I don't intend to give it even 1% publicity).

What’s curious is that each solution on the market, in their rush to make money, does everything possible to cover up the poor PHP code they contain, often obfuscating not just the panel code but also shady and often malicious scripts, which a streaming service provider could hardly audit.

These panels use modified libraries, and while some may be open-source, they compile them however they please, allowing them to contaminate the final product with who knows what.

So, I ask you, the average user, how do you blindly trust something you have no idea where it comes from or what its true purpose is? You install it on your server, where you hold the crown jewels of your business, making it incredibly easy for them to catch you.

I also understand that the business model for many is to lock down a tool and charge as much as they can.

But I prefer to adopt the model currently used in the crypto world: you can create something great and make the code open-source to ensure that it can be audited, with experts guaranteeing that nothing is wrong, while monetizing through specific support.

Just like there are open-source crypto wallets where companies can profit from specific developments or advanced technical support, I could create a panel from scratch with the best technology and practices available.

The idea is floating around in my head; I have the time, I have the means, and who knows—I might just make it a reality. It would be the end of those low-quality, insecure, scam-filled panels.

 

[KingPegasus]

It’s common to see complaints about certain panels regarding their lack of security, problems, bugs, etc. While many people might use the “official” versions or mods, patches, etc., the outcome is the same: service owners end up dealing with issues, spending a lot of money on maintenance, and ultimately facing a high risk of being detected or getting hacked along the way.

Over the years, there have been many leaks of source codes and services exposed to authorities, and they all had one thing in common: a panel that many idolized but in most cases ended up being a disappointment (I’ll avoid naming it because I don't intend to give it even 1% publicity).

What’s curious is that each solution on the market, in their rush to make money, does everything possible to cover up the poor PHP code they contain, often obfuscating not just the panel code but also shady and often malicious scripts, which a streaming service provider could hardly audit.

These panels use modified libraries, and while some may be open-source, they compile them however they please, allowing them to contaminate the final product with who knows what.

So, I ask you, the average user, how do you blindly trust something you have no idea where it comes from or what its true purpose is? You install it on your server, where you hold the crown jewels of your business, making it incredibly easy for them to catch you.

I also understand that the business model for many is to lock down a tool and charge as much as they can.

But I prefer to adopt the model currently used in the crypto world: you can create something great and make the code open-source to ensure that it can be audited, with experts guaranteeing that nothing is wrong, while monetizing through specific support.

Just like there are open-source crypto wallets where companies can profit from specific developments or advanced technical support, I could create a panel from scratch with the best technology and practices available.

The idea is floating around in my head; I have the time, I have the means, and who knows—I might just make it a reality. It would be the end of those low-quality, insecure, scam-filled panels.

I would be interested in another panel thats open source. Could definitely be a good thing.

 

[benjyteve]

I would be interested in another panel thats open source. Could definitely be a good thing.

Perhaps I'll bring this idea to life. With a strong community, I'm confident we can create a solid and stable platform.

 

[Moutamared]

better to build a panel using low level language, like c++ or something similar and fast into executing commands directly to the cpu, for better optimization and fatest zapping and so on, like the way that MPEGTV programmed, it makes it better in everything, the only thing that disapoint me is the design of the panel, which is not the best theme to come out for a panel.

 

[Kenxo]

while monetizing through specific support.

Early or later must pay something

companies can profit from specific developments or advanced technical support

Again,

I could create a panel from scratch with the best technology and practices available.

When and how and who will support ..

I have the means, and who knows—I might just make it a reality.

Can you send some example what are yr skills ...

It would be the end of those low-quality, insecure, scam-filled panels.

How long will take yr project ..

 

[Kenxo]

Perhaps I'll bring this idea to life. With a strong community, I'm confident we can create a solid and stable platform.

You are to late guys, we have seen this how started xtream ui and ended to XUI ONE .. also, CK mods and ended to 50-euro monthly fee and ,,, and many many started the same way ..
Odin and ended to 1000 euro Donation levels ..

 

[seagate]

Odin is the biggest waste that has disappointed many. no updates, no fixes.

 

[benjyteve]

Early or later must pay something

Again,

When and how and who will support ..

Can you send some example what are yr skills ...

How long will take yr project ..

My skills are sufficient for a project of this level, but it wouldn’t just be me. The idea is for it to be open source so that we can have contributions from people who are interested and knowledgeable about the subject. A good community ensures the success of this type of project.

Economically speaking, it will obviously be monetized, but we’re talking about support and specific developments, or even a marketplace around the panel, like plugins, extensions, etc.

Similar to other open-source technologies, certain adaptations are monetized, with the core being free to use, but support, extensions, etc. come at a price.

The timeline would depend on how much time I dedicate to the project, but I currently have the resources to give it good and prompt attention.

 

[Kenxo]

My skills are sufficient for a project of this level, but it wouldn’t just be me. The idea is for it to be open source so that we can have contributions from people who are interested and knowledgeable about the subject. A good community ensures the success of this type of project.

Economically speaking, it will obviously be monetized, but we’re talking about support and specific developments, or even a marketplace around the panel, like plugins, extensions, etc.

Similar to other open-source technologies, certain adaptations are monetized, with the core being free to use, but support, extensions, etc. come at a price.

The timeline would depend on how much time I dedicate to the project, but I currently have the resources to give it good and prompt attention.

I still don't understand this open-source project but anyway we wait on you ..
many needs migration tool to bring their bussines to this so how will this go as open source ..
Building all from 0 to end means all your code or you will need and search others to help ...this is another hard way on ..

 

[benjyteve]

You are to late guys, we have seen this how started xtream ui and ended to XUI ONE .. also, CK mods and ended to 50-euro monthly fee and ,,, and many many started the same way ..
Odin and ended to 1000 euro Donation levels ..

It’s never too late for a project; if that were the case, platforms that already had competition wouldn’t have made it to the market. Yet with their innovation and changes, they managed to position themselves.

Considering that the current panels are full of security issues, performance problems, etc., a new proposal will always be welcome, especially if there’s nothing obfuscated.

I believe this is the right moment to change how this is handled.

I still don't understand this open-source project but anyway we wait on you ..
many needs migration tool to bring their bussines to this so how will this go as open source ..
Building all from 0 to end means all your code or you will need and search others to help ...this is another hard way on ..

The database of many popular panels doesn't present a high challenge when it comes to migration, so the process of adopting this project can include a migration tool to ease the transition.

I'm working on the details, but I’m glad that many people are showing curiosity about the idea.

 

[Kenxo]

The database of many popular panels doesn't present a high challenge when it comes to migration, so the process of adopting this project can include a migration tool to ease the transition.

I'm working on the details, but I’m glad that many people are showing curiosity about the idea.

And yes, remember this that all this business doing those that are hungry for money so how you feed them all is a big story ...
Wish you all the best and Goodluck .
I will come time to time to see the progres ..

 

[benjyteve]

And yes, remember this that all this business doing those that are hungry for money so how you feed them all is a big story ...
Wish you all the best and Goodluck .
I will come time to time to see the progres ..

Thanks for the good vibes!

And yes, there are many sharks out there, and they don’t like it when the waters are stirred too much.

 

[benjyteve]

I want to provide more details as I get a clearer understanding of the idea, of course. I also want to clarify that the project hasn’t officially started, but it will soon. Among the things I’m defining are:

1. The fully functional base project will be open-source, hosted in a secure repository, and licensed for use, modification, extension, etc. (It could be the MIT License).
2. It will start with the general architecture so that those familiar with the topic and who wish to collaborate can have a clear overview.
3. Next will be the backend, utilizing the best available technologies to meet the most critical functionalities of streaming software, adhering to principles of security, high availability, scalability, performance, etc.
4. I want everything to come pre-configured with the necessary settings to launch with minimal effort, but advanced users will have the option to modify the lower layers, such as the restreamer, etc.
5. I’ll create a wrapper, an API that connects with this core and allows it to be manipulated based on the permission level of the role, so it can be extended, integrated, etc.
6. Of course, I will need to include support for DRM, and this topic has its own peculiarities that I’ll detail as I make progress on it.
7. Everything that is not part of the core itself, like user management, resellers, credit systems, sources, etc., will be added as plugins. With this approach, we can develop and integrate with any system into the base.

Scalability and security will have their own dedicated sections. I have experience in both areas, both defending and attacking, so I have an idea of how to implement them in the best way. However, at this stage, any expert can contribute. It's essential that the critical points of the project be audited by the community, so we can all ensure that the build each person uses is truly secure and not tampered with, avoiding any negative consequences.

Oh, by the way, any name suggestions for the project are warmly welcome!

 

[KingPegasus]

I want to provide more details as I get a clearer understanding of the idea, of course. I also want to clarify that the project hasn’t officially started, but it will soon. Among the things I’m defining are:

1. The fully functional base project will be open-source, hosted in a secure repository, and licensed for use, modification, extension, etc. (It could be the MIT License).
2. It will start with the general architecture so that those familiar with the topic and who wish to collaborate can have a clear overview.
3. Next will be the backend, utilizing the best available technologies to meet the most critical functionalities of streaming software, adhering to principles of security, high availability, scalability, performance, etc.
4. I want everything to come pre-configured with the necessary settings to launch with minimal effort, but advanced users will have the option to modify the lower layers, such as the restreamer, etc.
5. I’ll create a wrapper, an API that connects with this core and allows it to be manipulated based on the permission level of the role, so it can be extended, integrated, etc.
6. Of course, I will need to include support for DRM, and this topic has its own peculiarities that I’ll detail as I make progress on it.
7. Everything that is not part of the core itself, like user management, resellers, credit systems, sources, etc., will be added as plugins. With this approach, we can develop and integrate with any system into the base.

Scalability and security will have their own dedicated sections. I have experience in both areas, both defending and attacking, so I have an idea of how to implement them in the best way. However, at this stage, any expert can contribute. It's essential that the critical points of the project be audited by the community, so we can all ensure that the build each person uses is truly secure and not tampered with, avoiding any negative consequences.

Oh, by the way, any name suggestions for the project are warmly welcome!

Very good details. Basically going to integrate the top requested features Pele ask for. Faster on demand speeds, migration from different panel, etc etc.
The name will need to be something catchy or even simple. XCD (Xtream Codes Dynasty)
Maybe something better. Or whatever you will suggest considering you will be the backbone of this panel

 

[Kenxo]

Xtream Codes Dynasty

XCK Xtream Codes Killer is the best ..as will kill all modes.

I want to provide more details as I get a clearer understanding of the idea, of course. I also want to clarify that the project hasn’t officially started, but it will soon. Among the things I’m defining are:

1. The fully functional base project will be open-source, hosted in a secure repository, and licensed for use, modification, extension, etc. (It could be the MIT License).
2. It will start with the general architecture so that those familiar with the topic and who wish to collaborate can have a clear overview.
3. Next will be the backend, utilizing the best available technologies to meet the most critical functionalities of streaming software, adhering to principles of security, high availability, scalability, performance, etc.
4. I want everything to come pre-configured with the necessary settings to launch with minimal effort, but advanced users will have the option to modify the lower layers, such as the restreamer, etc.
5. I’ll create a wrapper, an API that connects with this core and allows it to be manipulated based on the permission level of the role, so it can be extended, integrated, etc.
6. Of course, I will need to include support for DRM, and this topic has its own peculiarities that I’ll detail as I make progress on it.
7. Everything that is not part of the core itself, like user management, resellers, credit systems, sources, etc., will be added as plugins. With this approach, we can develop and integrate with any system into the base.

Scalability and security will have their own dedicated sections. I have experience in both areas, both defending and attacking, so I have an idea of how to implement them in the best way. However, at this stage, any expert can contribute. It's essential that the critical points of the project be audited by the community, so we can all ensure that the build each person uses is truly secure and not tampered with, avoiding any negative consequences.

Oh, by the way, any name suggestions for the project are warmly welcome!

What you wrote is like is all ready just need to be published ..or maybe I am wrong, and if I am wrong when is first beta date ..

A puppet theater ...
Sorry to make this comparations but , in my town was born some new shops as a trend so called all for 99 cent ..
But when you come in is not true that all inside products are 99 cents but just some of them so mostly are 100 time higher ..
Anyway, they are still alive and operational and still someone goes there to find something for 99 cent ..

 

[benjyteve]

XCD and XCK sound like great name options.

I’ve just outlined my idea along with a rough roadmap that I have in mind. As I mentioned, there isn’t an official start date yet, but it’s definitely something I’m eager to begin soon. I’m feeling more motivated as the concept develops.

The vision for building a community is centered on staying true to the core principles—keeping this foundation free, open-source, and transparent, with no hidden agendas or traps.

 

[HyperX]

I want to provide more details as I get a clearer understanding of the idea, of course. I also want to clarify that the project hasn’t officially started, but it will soon. Among the things I’m defining are:

1. The fully functional base project will be open-source, hosted in a secure repository, and licensed for use, modification, extension, etc. (It could be the MIT License).
2. It will start with the general architecture so that those familiar with the topic and who wish to collaborate can have a clear overview.
3. Next will be the backend, utilizing the best available technologies to meet the most critical functionalities of streaming software, adhering to principles of security, high availability, scalability, performance, etc.
4. I want everything to come pre-configured with the necessary settings to launch with minimal effort, but advanced users will have the option to modify the lower layers, such as the restreamer, etc.
5. I’ll create a wrapper, an API that connects with this core and allows it to be manipulated based on the permission level of the role, so it can be extended, integrated, etc.
6. Of course, I will need to include support for DRM, and this topic has its own peculiarities that I’ll detail as I make progress on it.
7. Everything that is not part of the core itself, like user management, resellers, credit systems, sources, etc., will be added as plugins. With this approach, we can develop and integrate with any system into the base.

Scalability and security will have their own dedicated sections. I have experience in both areas, both defending and attacking, so I have an idea of how to implement them in the best way. However, at this stage, any expert can contribute. It's essential that the critical points of the project be audited by the community, so we can all ensure that the build each person uses is truly secure and not tampered with, avoiding any negative consequences.

Oh, by the way, any name suggestions for the project are warmly welcome!

You don't understand of the amount of work, in money it is at least 200K USD and 2-3 years of development. Better to take core of some existing panel talk with founders and maybe they decide to work with you, but Goodluck.

 

[benjyteve]

You don't understand of the amount of work, in money it is at least 200K USD and 2-3 years of development. Better to take core of some existing panel talk with founders and maybe they decide to work with you, but Goodluck.

I understand the workload, effort, and resources required. I have experience in the field, having worked with IPTV-related tools for years, and I am aware that building a panel from scratch is full of challenges and is time-consuming.

My principle is to offer this foundation for free and as open source, and that’s how I maintain the idea. If I make it dependent on whether a founder wants to participate, I would need that certainty. Otherwise, and I believe it’s unlikely that someone already in the market would want competition, I would still need to start my own project.

 

[Delta19]

I am sure you will succeed because you have these qualities...the most important thing is open source, no monopoly and no one should take over this project, even here

 

[benjyteve]

Initially, the load balancing (balancers) feature was a significant milestone in infrastructure development. Although in some well-known panels it has been prone to issues like latency, disconnections, exposure to intrusions, and more, it remains a crucial part of these systems' architecture.

After extensive analysis over time, I’ve pinpointed critical improvements needed in this layer, and I am committed to developing it with a focus on solving these persistent problems.

One key feature that will be part of the breakthroughs in this project is the integration of a custom CDN solution. Many are quick to use any available CDN they find online, which often carries risks such as IP exposure or even server blacklisting.

My plan is to add this critical layer, not just for the obvious benefits:

• Caching for optimized performance.
• High availability across geographical zones.
• Mitigating server attacks (DDoS).
• And more.

But more importantly, I am focused on protecting the servers' IPs. It’s widely known that many governments enforce service blocks by blacklisting IPs, and this layer will address precisely that by allowing you to:

• Rotate IPs regularly.
• Never expose the real server IP.
• Easily replace this layer (small nodes) instead of your entire infrastructure, saving you both costs and time.

In my research and development toolbox, I also have P2P streaming modules that I worked on in the past, but that’s something I’ll unveil further down the road.

For now, I leave these thoughts here, open to interpretation and debate.