Technologies

Technologies that support business

We choose tools based on project requirements - not trends. We focus on performance, security, and maintainability.

Technologies

Technology ecosystem

We choose tools for the goal - we don't build around a trendy framework. Here are the technologies we work with every day.

VueNuxtTypeScriptNode.jsPythonPHPLaraveln8nPostgreSQLMySQLRedisDockerKubernetesLinuxWindowsNginxCloudflareAWSAzureGitHubJiraFreshdeskREST APIGraphQLCI/CDAI APIsLLMAutomations

Stack

Tools we work with

Proven open-source technologies and cloud platforms - without unnecessary vendor lock-in.

  • Vue.js
    Vue.js
  • Nuxt
    Nuxt
  • TypeScript
    TypeScript
  • Node.js
    Node.js
  • Python
    Python
  • PHP
    PHP
  • Laravel
    Laravel
  • PostgreSQL
    PostgreSQL
  • Redis
    Redis
  • Docker
    Docker
  • Kubernetes
    Kubernetes
  • Linux
    Linux
  • Windows
    Windows
  • Nginx
    Nginx
  • AWS
    AWS
  • Cloudflare
    Cloudflare
  • GitHub
    GitHub
  • Jira
    Jira
  • Freshdesk
    Freshdesk
  • n8n
    n8n
  • OpenAI
    OpenAI

Philosophy

We choose technologies for the problem

We're not tied to one framework - we pick tools that best fit the project.

We rely on proven, maintainable technologies with active communities. For web apps we often choose Vue/Nuxt; for backend Node.js or Python - depending on performance and integration needs.

For infrastructure we work with Docker, Kubernetes, Terraform, and CI/CD tools matched to the client's team.

  • Frontend: Vue, Nuxt, TypeScript
  • Backend: Node.js, Python, REST/GraphQL
  • Databases: PostgreSQL, MySQL, Redis, MongoDB
  • Cloud: Docker, K8s, AWS, GCP, VPS

Practices

How we work with code and infrastructure

Standards that keep projects healthy for years.

Repositories with clear structure, automated tests in the pipeline, semver and changelog on releases. Secrets outside code, access following least privilege.

For clients with their own dev team - we leave code and docs in a state that enables smooth handover.

  • Git flow and code review
  • CI/CD on every production project
  • Secure secrets management
  • Monitoring and logging from first deployment

FAQ - Technologies

Questions about our tech stack

About the tools we use and why.

If you have a standard - we adapt. If not - we propose a stack for project requirements and maintenance team skills.

We focus on web applications and PWAs. For mobile needs we integrate with native apps via API.

Yes - code and documentation belong to the client per contract. We don't use a closed vendor lock-in model.

Let's build technology that makes a difference

Tell us what you want to improve, automate, or build. We'll help turn your idea into a stable solution with business, technical, and cost sense.