Main content
EnglishRomână
Contact
EnglishRomână

Software engineering studio in Cluj-Napoca

ELASTO TECHNOLOGIES builds AI agents, custom software and the cybersecurity around both, from Cluj-Napoca, EU. The engineers on the first call build the system.

Project briefWork
Company
ELASTO TECHNOLOGIES S.R.L.
Studio
Cluj-Napoca, Romania, EU
Founder
George Flutur
Languages
English, Romanian, French

The engineers on the first call write the code

A senior engineer leads every project from the first call to production, with the team behind them, one reviewed pull request at a time.

FIG. 1How an engagement runsEvery service
How an engagement runs, from the first call to maintenance.A first call leads to a written, priced scope. The team builds it as reviewed pull requests, and specialists join through the same review. Production runs in the client's accounts, with a handover of code, accounts and runbook, and maintenance is optional. The same lead engineer stays from the first call to production.First callScopingWritten scopePricedBuildPull requestsProductionClient's accountsMaintenanceOptionalSame lead

Repositories and accounts in the client's name

Nothing runs on a personal account, so a later team can take over from the runbook.

FIG. 2What stays with the client
What stays with the client: repository, cloud and AI accounts, domains and apps, credentials and the runbook.All five sit in the client's accounts from the start. ELASTO works through delegated access, and a later team can take over from the runbook.RepositoryCloud and AIDomains and appsCredentialsRunbookDeploy and restoreELASTODelegated accessNext teamTakes overIn the client's accounts from the start

Handover checklist

  • The repository

    With its full commit history, in the client's GitHub or GitLab organisation.

  • Cloud and AI accounts

    Hosting, databases and model providers, billed to and owned by the client.

  • Domains and app store listings

    Registered in the client's name, with the client as account holder.

  • Prompts and agent workflows

    Versioned in the repository, with the evaluation sets used to test them.

  • Credentials

    Handed over through a password manager, never in email or chat.

  • Runbook and architecture notes

    Deploy, restore and incident steps a new team can follow.

  • Ownership

    Code and documentation pass to the client on full payment, as the contract sets out.

Continuity on every project

  • Written down

    Architecture notes, a runbook and a README that a competent team can follow without a call.

  • In the client's accounts

    Nothing runs on a personal account. Repositories, cloud projects and API keys sit with the client from the start.

  • Shared by the team

    Several engineers know each system through code review, and a maintenance agreement keeps them close to it, with response times in the contract.

A note from the founder

I started ELASTO so that the people who scope a system are the people who build it. Too much gets lost between the sales call and the first commit when those are two different groups.

My background is firmware, mobile apps and web platforms. Agents joined that toolset later and get the same treatment as everything else: logs, tests and a person approving anything that cannot be undone.

Every change reaches the codebase as a pull request reviewed by an engineer who knows the system, whoever wrote it.

George Flutur, Founder, ELASTO TECHNOLOGIES S.R.L.

Working with ELASTO

Who works on a project

A senior engineer leads every project from the first call to production, with the team behind them. Specialists join for extra capacity or a specific skill, and every change goes through the same review before it merges.

Continuity on every project

Several engineers know each system, because every change is reviewed by someone other than its author. The code, the accounts and the documentation sit with the client, so any competent team can take over from the runbook.

A maintenance agreement keeps engineers who already know the system on it. The handover checklist lists what stays with the client.

Progress during a project

Progress is visible in the repository: every change arrives as a pull request with a description, and a staging environment runs the current build.

Written updates follow a rhythm agreed at the start, and decisions that change the scope are confirmed in writing.

Support after launch

After launch, a maintenance agreement can cover monitoring, security updates, fixes and small changes. Its monthly scope and response times are written into the contract before launch, so nothing depends on goodwill.

Location, time zone and clients outside Romania

ELASTO works from Cluj-Napoca, Romania, on Eastern European Time (UTC+2, UTC+3 in summer). Romanian afternoons overlap with US East Coast mornings.

Calls, documents and contracts can be in English, Romanian or French. The registered office, tax code and trade register number are on the company details page.

Every brief reaches the team that builds it

A few lines are enough to start.

Project brief
Work
Email
contact@elastoapps.com
Studio
Cluj-Napoca, Romania, EU