My old Vinted Bot on GitHub is no longer maintained: why I built Fyndit

Some time ago, I published an open-source project on GitHub for creating a Discord bot that monitors new Vinted listings.

The project, available in the vinted-discord-bot repository, was my first serious attempt to develop a fast Vinted bot that was accessible to and configurable by the community.

Developers and resellers have since used, modified and shared the repository. It passed 180 stars on GitHub, showing the interest behind searches such as Vinted bot free, Vinted bot GitHub and Vinted bot create your own.

Today, however, I want to be completely transparent: this repository is no longer maintained and may no longer work correctly.

I now focus my work on Fyndit, a much more advanced version designed for resellers who want to monitor Vinted seriously and grow their operation at a larger scale.

Why is the old Vinted Bot GitHub repository no longer maintained?

The GitHub repository was primarily an early public prototype.

It could monitor selected Vinted searches, manage monitors and send new listings to Discord channels. Its stack included JavaScript, Docker, MongoDB, a Linux server and rotating proxies.

The project was a useful introduction to the way a monitoring bot works. It also served as an educational resource for developers who wanted to understand how to connect a listing-monitoring system to Discord.

A public prototype, however, is not the same as a dependable service used by resellers every day.

Vinted changes regularly. Technical responses, data structures, regional behaviour and access constraints can all evolve. A seemingly minor change can slow a monitor, cause it to miss listings or make part of the system unusable.

Maintaining several versions of the same project for free would therefore require an enormous amount of time. I chose to invest that time in one actively developed platform: Fyndit.

Building your own Vinted bot is far more complicated than it appears

Many people now search for Vinted bot DIY, Vinted bot create your own, Vinted bot GitHub and Vinted bot free. They also want to know how to create a Vinted bot with ChatGPT or code one with Claude Code.

Artificial-intelligence tools can certainly help generate code, explain an error or produce an initial prototype quickly.

Using ChatGPT or Claude Code, however, is not enough to build a fast, stable and competitive Vinted bot.

An AI assistant may generate a few JavaScript or Python files. It does not automatically turn those files into production infrastructure that runs continuously, supports many users and remains effective when conditions change.

The initial code is only a small part of the work.

Those generated files still need to be deployed, connected to persistent storage, observed under real traffic and protected against partial failures. A prototype that returns one successful result does not prove that every saved search will keep receiving complete results throughout the day.

Production quality also requires documentation, controlled releases and a way to compare performance before and after every change. Without that operational layer, a small technical change can silently reduce detection quality long before a visible error appears.

What a modern Vinted bot actually has to manage

1. Infrastructure that is always available

A bot used for sourcing needs to operate 24 hours a day.

That requires properly configured servers, availability monitoring, controlled restarts, installed updates and checks that the different services continue to communicate correctly.

Running a script on a personal computer may work for a test. It is generally not sufficient for a consistent service that remains usable at scale.

2. Proxy management

Searches for Vinted bot proxies are common for a reason: network quality plays an important part in the performance of a monitoring system.

Buying a list of proxies and adding it to a configuration file is not enough. Their availability, speed, stability and behaviour in different regions all need to be monitored.

Proxies are also a recurring expense. A DIY system that initially appears free can quickly require a monthly budget for hosting, networking, databases and monitoring tools.

3. Speed without sacrificing reliability

A slow monitor loses much of its value. For the most competitive listings, a few seconds can make the difference.

Simply increasing request frequency is not a viable architecture.

The system must process results quickly, avoid duplicates, distribute notifications, manage queues and continue operating when one component encounters an error.

Real speed therefore depends on the entire infrastructure, not merely on a few lines of code advertised as “zero delay”.

4. Databases and processing queues

A Vinted bot has to store monitors, preferences, users, listings already detected and actions waiting to be processed.

At a small scale, a simple database may be sufficient. As the number of searches and users increases, the system must handle concurrency, indexes, simultaneous writes, expiry rules and possible processing delays.

Without that architecture, the bot may send the same listing more than once, ignore some results or slow down as activity increases.

5. Differences between countries and regions

Vinted does not behave in exactly the same way in every market.

Domains, categories, parameters, languages, currencies and available data may differ. A service for European resellers must account for several regions instead of relying on one hard-coded configuration.

That compatibility requires continuous testing and market-specific maintenance.

6. Notifications and automation

Sending a simple URL to a Discord channel is relatively easy.

Building a complete experience is much more complex: detailed filters, information presentation, photographs, action buttons, permissions, connected accounts, automated offers, automated purchases and priority processing.

Every additional feature creates new error scenarios and requires security, validation and tracking mechanisms.

7. Monitoring and maintenance

A bot can appear to be working while it is actually missing some listings.

Delays, errors, the volume of detected results, server health and the performance of every component must therefore be monitored.

When a problem appears, the team needs to identify and fix it quickly. This continuous maintenance, which users rarely see, takes the most time.

A free Vinted bot is not really free to operate

A project's code can be available for free on GitHub. That does not make running it free.

Operating the old repository properly already required:

• a VPS or Linux machine available continuously;
• rotating proxies;
• Docker;
• a MongoDB database;
• a Discord bot and server;
• programming and system-administration knowledge;
• time to diagnose errors;
• regular maintenance.

Even with a free Vinted bot from GitHub, the user remains responsible for infrastructure expenses and development time.

The server is not always the main cost. The time required to understand the code, fix problems, adapt the system and verify that it is not missing listings can cost far more.

From the old GitHub repository to Fyndit

The old GitHub bot was an important first step.

It allowed me to test an architecture, understand user needs and observe the limitations of a public monitor installed separately by every user.

Fyndit is the professional continuation of that work.

Instead of distributing only source code that each user must install and maintain, Fyndit provides an operational platform. Our team manages the infrastructure, updates and optimisations directly.

Users can benefit from:

• live Vinted monitors;
• filters for keywords, price, country, seller and condition;
• instant Discord alerts;
• buttons for acting directly from Discord;
• purchase and offer actions where available;
• average item-price analysis;
• seller verification;
• support for multiple regions;
• solutions for resellers operating at a larger scale.

The goal is no longer simply to demonstrate that a listing can be detected. It is to provide a tool fast, simple and stable enough to become part of a real reselling operation.

Can the old Vinted Bot GitHub repository still be used?

The repository remains public for educational purposes.

You may still inspect its architecture, download the code and conduct your own experiments. It can be a starting point for learning JavaScript, Docker, MongoDB or Discord bot development.

You should nevertheless assume that the project is deprecated.

Some parts may no longer behave as intended. This old version receives no regular fixes, installation support or performance guarantee.

It is therefore not recommended as the foundation of a reselling business that depends on monitoring speed and availability.

Can ChatGPT and Claude Code create a Vinted bot?

These tools can help you understand the repository, generate functions or correct certain errors.

They are useful for accelerating development, but they do not replace:

• architecture design;
• infrastructure selection and management;
• testing under real operating conditions;
• performance supervision;
• proxy maintenance;
• database management;
• incident resolution;
• continuous updates;
• compliance with the rules of the platforms being used.

In other words, asking an AI to “create a Vinted bot” can produce a technical demonstration. It does not automatically produce a fast, dependable service for hundreds or thousands of monitors.

Why use Fyndit instead of building your own bot?

Building your own bot can make sense for learning and experimentation.

For a reseller, the question is different: how much time do you want to spend on technical maintenance instead of sourcing, analysing products and reselling them?

With a DIY solution, you are responsible for servers, proxies, code, bugs and outages.

With Fyndit, you use maintained infrastructure designed around reseller needs. You can start with one free monitor, receive Discord alerts and move to more advanced features as your operation grows.

Discover Fyndit and start for free

Frequently asked questions

Does Teddy's Vinted bot on GitHub still work?

The repository is still accessible, but it is no longer actively maintained. It may therefore fail to work correctly and has no performance guarantee.

Is the repository still free?

Yes. The public repository's code remains available on GitHub. Its hosting, proxies, database and maintenance are not free, however.

Can I create my own Vinted bot with this code?

You may use it as an educational resource and technical starting point. Knowledge of JavaScript, Docker, MongoDB, Linux and network administration will be necessary to adapt and maintain it.

Do I need proxies for a DIY Vinted bot?

A large-scale monitoring system generally requires serious network infrastructure. Selecting, rotating and supervising proxies is a complex subject and recurring expense, and it must be managed in accordance with the applicable rules.

Can I create a Vinted bot using only ChatGPT or Claude Code?

These tools can accelerate code writing and debugging. On their own, they do not manage hosting, supervision, databases, proxies, incidents or daily maintenance.

Is there still a free Vinted bot?

Fyndit offers a plan that lets you begin for free with one monitor and Discord alerts. It provides a way to test the service without installing and maintaining the old repository yourself.

Conclusion

The first Vinted bot on GitHub was an important experiment and a useful foundation for many developers.

Developing a genuinely fast Vinted bot, however, does not stop after ChatGPT or Claude Code generates a few files. It requires infrastructure, proxies, databases, processing systems, supervision and, above all, continuous maintenance.

That is exactly why the old repository is no longer maintained.

My work is now focused on Fyndit: a more complete, actively developed platform for resellers who want to use Vinted at a larger scale without managing the entire technical layer themselves.

Start using Fyndit for free

Fyndit is an independent service and is not affiliated with Vinted. Every user remains responsible for how they use the service and for complying with the terms of the platforms concerned.