Here you will find answers to the most frequent technical and organizational questions about our activities.

Section 1: About our model and philosophy
Q1: Is it really free? What's the catch?
A: Yes, it's absolutely free. There are no hidden fees, trial periods that then turn into paid ones, or obligations to purchase any services in the future. There is only one catch: we help projects that, in our opinion, are useful and interesting for the IT community. Our motivation is to develop technology, open knowledge, and strengthen the community of enthusiasts.

Q2: How do you exist and why do you provide services for free?
A: Our activities are supported by several sources:

Grants and sponsorship: We receive support from organizations and companies interested in developing the open-source ecosystem.

Voluntary contributions from the community: The part of the community that values our work supports us financially on a voluntary basis.

Expert capital: For our engineers, this is an opportunity to work with interesting and complex technical tasks, enhance their own expertise and create a public portfolio.

Q3: Do you compete with commercial hosting and DevOps companies?
A: No, our target audience and goal are completely different. Commercial companies work to make a profit from their business. We are a non-profit initiative aimed at helping those who do not have a budget, but have an innovative project, an early-stage startup, or a valuable open-source tool. Rather, we complement the ecosystem by giving life to projects that might otherwise not have taken place.

Section 2: Technical details and features
Q4: What technology stacks and programming languages are you working with?
A: Our expertise covers most modern and classic stacks.:

Server side: Linux/BSD, Kubernetes, Docker, Nginx/Apache, PostgreSQL, MySQL, Redis, RabbitMQ.

Backend languages: Python (Django, FastAPI), JavaScript/TypeScript (Node.js, NestJS), Go, Java, Rust, PHP (Laravel, Symfony), C# (.NET).

Frontend: React, Vue.js, Angular, Svelte.

Other: We have experience working with monitoring systems (Prometheus, Grafana), CI/CD tools (GitLab CI, GitHub Actions), and cloud providers (AWS, GCP, Azure — at the configuration level).

Q5: What server infrastructure do you use?
A: We maintain our own fleet of servers in Tier III data centers, as well as use the resources of cloud providers provided to us through partner programs. This allows us to ensure fault tolerance, geographical distribution, and high throughput.

Q6: Do you only provide bug fixes or are you also engaged in full development from scratch?
A: Our main specialization is the refinement, optimization and support of existing projects. We are not engaged in a complete turnkey development according to your specifications. However, we can help with:

Creating an MVP for an already formed idea.

Integration of complex modules into an existing codebase.

Fixing critical errors that prevent the launch of the project.

Refactoring and optimizing the code for the finished product.

Section 3: Work process and conditions
Q7: What does the collaboration process look like?
A: The process is as transparent as possible and built on agile principles:

Application: You describe your task through the form on the website, in as much technical detail as possible.

Technical audit: Our team conducts an initial analysis of the feasibility and complexity of the implementation.

Prioritization: We consider the application in the context of its usefulness to the community, complexity, and our current capabilities.

Development: If the project is accepted, we create a private repository, a branch for the task and proceed with implementation, maintaining constant communication with you.

Code Review & Delivery: All changes are subject to a strict internal code review before assembly. The result is provided to you in the form of a pool request or directly to the repository.

Documentation: All changes made are documented in detail.

Q8: How do you decide who to help? Are there any priorities?
A: Yes, we prioritize based on the following criteria:

High priority: Critical vulnerabilities and bugs in popular open-source projects; projects with obvious and great benefits for the community.

Medium priority: Interesting technical tasks; startups at the MVP stage; projects with an active community.

Low priority: Personal projects with a narrow focus; tasks that require excessive resources with no apparent benefit to the ecosystem.

Q9: Do you guarantee your work?
A: We provide quality assurance at the professional community level. It means:

We correct any mistakes we make in the course of our work, free of charge and as a matter of priority.

We do not provide commercial SLAs (Service Level Agreements) for server uptime, but we do our best to ensure maximum stability, as our reputation is important to us.

All our work is transparent and undergoes strict code review.

Q10: Is my code still confidential?
A: Absolutely. We follow a strict privacy policy. Only directly assigned engineers have access to your code. By default, we work through private repositories. After completing the work, you can continue to develop the project yourself, and we will delete all copies of it from our systems, if necessary.

Didn't find the answer to your question?
Contact us directly via [telegram link/discord/email], and our technical team will give you a detailed response.