DevAssistant

A non-standard approach always delivers great results. Here is a case study we contributed to.

A cool work tool made by colleagues, we also enjoy using it.

Not putting up with inconvenience, but customizing an existing product to fit our own needs – that's something we know how to do.

At Evrone, we use Yandex.Tracker for time tracking. It's a perfectly good system, but there were a few nuances that, let's say, bothered us. Small things, but in everyday work, they can become critical.

Instead of waiting for the system to be updated, we built our own time tracking tool that integrates with Tracker. No server-side dependencies – just a client-side app that works through Yandex authorization.

Timesheet is a lightweight add-on that pulls data from Tracker and presents it the way we find convenient. No servers, no infrastructure – just a client and Yandex login.

What's inside:

✅Time entries can now be edited
✅ Reports by tasks and projects broken down by day, week, month
✅ Active tasks are pulled automatically
✅ Filters by queue, status, and project
✅ Support for two languages and time zones
✅ Input in minutes by default – which is simply convenient

But here's the thing: we're well aware that Tracker pain isn't just our pain. That's why Timesheet is open source. Any team can take it, tweak it for their own needs, and use it.

All the details are here: https://evrone.com/blog/timesheet

More than 7,000 stars and 600+ forks on GitHub confirm that this template has clearly struck a chord with teams building scalable Go services.

Our Go open-source template has surpassed more than 7,000 stars and 600 forks on GitHub – and those numbers are still climbing!

We built go-clean-template to solve a persistent pain: how to start a new service so that a year later, its code hasn’t turned into a tangled labyrinth of interdependencies. Our goal is to provide a foundation that establishes a clear Clean Architecture structure from day one – isolating business logic and keeping the project scalable.

That’s exactly why the developer community has embraced it. Behind every fork is a real project that relies on this template to maintain architectural clarity and development velocity. And our steady stream of updates (over 40 releases and counting!) shows the project is actively maintained and evolving right alongside the Go ecosystem.

This is our contribution to the community – and a tangible example of our expertise in building clean, resilient systems.

→ Explore the template and start your next project with solid architecture: github.com/evrone/go-clean-template

As usual, we're sharing an interesting project that we became a part of.

When your expensive GPUs are idling and teams are stuck waiting in line...

Does this sound familiar? A European research lab came to us with the same problem. Their powerful AI video cards were only 10-20% utilized, while multiple teams were manually coordinating access through managers. It was slow and opaque.

Our solution:

✔️ We didn't try to sell them a ready-made product. First, we tested different approaches on their actual hardware and workloads.

✔️ In just 2 months, we built and deployed a unified platform based on Kubernetes and open-source software (creating no vendor lock-in).

✔️ Now their GPUs are a shared, secure, and transparent resource. AI tasks run in parallel instead of waiting in line. Engineers focus on their work instead of manual resource management.

The result: the lab finally got a return on their hardware investment. And all of this runs on their own infrastructure, under their complete control.

Are you looking at your server utilization charts and wondering what to do next? Let's discuss.

https://evrone.com/cases/relab