How does working with Tectryx start?

With a conversation of about thirty minutes in which you describe what you are dealing with and we ask questions. Afterwards you get a written assessment: what we consider feasible, which path we would suggest and what order of effort to expect. That conversation is free and comes with no obligation.

Do you also work with small businesses?

Yes, frequently. A large share of our work consists of bounded projects for small and medium-sized businesses: a line-of-business application, an interface between two systems, a shop that needs to become maintainable again. That does not take a large team, it takes one person who owns the result and draws on our network when needed. It starts with a first conversation and, if it fits, a small first project at a fixed price.

How quickly can you start?

It depends on the core team's workload and on which skills are needed. Smaller bounded pieces of work can often be scheduled at short notice, larger engagements need lead time. In the first conversation you get a realistic date, not a convenient one.

Do you work on site or remotely?

Mostly remotely. Tectryx Solutions GmbH is based in Berlin and serves German-speaking Europe. We come on site where presence makes a difference: kickoff, workshops, critical handovers.

Which languages do you work in?

German and English, in project communication as well as in documentation. Mixed teams are normal for us, not an exception.

Do you work at a fixed price or time and materials?

Both, depending on how clearly the goal is defined. A bounded piece of work with stable requirements can be quoted at a fixed price. Ongoing development where priorities shift along the way is billed by effort, because a fixed price there only creates the appearance of certainty. Whichever model we propose, we explain why.

Who owns the source code and infrastructure?

You do. We work in your repositories or hand them over at project start. Infrastructure is defined as code and lives with you as well. Open-source components we use are documented together with their licences.

What happens at the end of a project?

An orderly handover: documented architecture decisions, a runbook, an onboarding path and a joint walkthrough with the team taking over. We stay on for maintenance and support if you want, but you should not have to depend on it.

Who actually works on our project?

A permanent core team owns architecture and accountability. For peak loads and niche topics, freelancers from a network we have worked with before join in. You know in advance who is involved and meet them before you commit.

Which technologies do you work with?

We work with whatever fits the project best. Problems can be solved in many ways and are not limited to programming languages: sometimes the right answer is an existing tool, an integration, an automation or an adjusted process rather than new code. We frequently use TypeScript, Vue, Nuxt, Node.js, PHP and Go, and in operations Docker, Terraform and automated deployment pipelines. The choice follows your project and what your team can maintain afterwards.

Where is our data hosted?

As a rule, within the European Union. We choose the provider with you based on your requirements around data protection, cost and existing knowledge in your team. Data processing agreements under GDPR are part of the standard process.

Do you take on existing systems?

Yes. An assessment of code, dependencies and operations comes first and sets out what is urgent, what is due in the medium term and what effort to expect. You decide on that basis.

Do you work with AI tools?

Yes, where they measurably contribute: in development itself and in client projects where automation or AI-supported workflows are part of the brief. Decisions about architecture and code stay with people, and we agree upfront which tools are permitted in your project.

Frequently Asked Questions - Working with Tectryx Solutions

Working together

How does working with Tectryx start?: With a conversation of about thirty minutes in which you describe what you are dealing with and we ask questions. Afterwards you get a written assessment: what we consider feasible, which path we would suggest and what order of effort to expect. That conversation is free and comes with no obligation.
Do you also work with small businesses?: Yes, frequently. A large share of our work consists of bounded projects for small and medium-sized businesses: a line-of-business application, an interface between two systems, a shop that needs to become maintainable again. That does not take a large team, it takes one person who owns the result and draws on our network when needed. It starts with a first conversation and, if it fits, a small first project at a fixed price.
How quickly can you start?: It depends on the core team's workload and on which skills are needed. Smaller bounded pieces of work can often be scheduled at short notice, larger engagements need lead time. In the first conversation you get a realistic date, not a convenient one.
Do you work on site or remotely?: Mostly remotely. Tectryx Solutions GmbH is based in Berlin and serves German-speaking Europe. We come on site where presence makes a difference: kickoff, workshops, critical handovers.
Which languages do you work in?: German and English, in project communication as well as in documentation. Mixed teams are normal for us, not an exception.

Approach and contracts

Do you work at a fixed price or time and materials?: Both, depending on how clearly the goal is defined. A bounded piece of work with stable requirements can be quoted at a fixed price. Ongoing development where priorities shift along the way is billed by effort, because a fixed price there only creates the appearance of certainty. Whichever model we propose, we explain why.
Who owns the source code and infrastructure?: You do. We work in your repositories or hand them over at project start. Infrastructure is defined as code and lives with you as well. Open-source components we use are documented together with their licences.
What happens at the end of a project?: An orderly handover: documented architecture decisions, a runbook, an onboarding path and a joint walkthrough with the team taking over. We stay on for maintenance and support if you want, but you should not have to depend on it.
Who actually works on our project?: A permanent core team owns architecture and accountability. For peak loads and niche topics, freelancers from a network we have worked with before join in. You know in advance who is involved and meet them before you commit.

Technology and data protection

Which technologies do you work with?: We work with whatever fits the project best. Problems can be solved in many ways and are not limited to programming languages: sometimes the right answer is an existing tool, an integration, an automation or an adjusted process rather than new code. We frequently use TypeScript, Vue, Nuxt, Node.js, PHP and Go, and in operations Docker, Terraform and automated deployment pipelines. The choice follows your project and what your team can maintain afterwards.
Where is our data hosted?: As a rule, within the European Union. We choose the provider with you based on your requirements around data protection, cost and existing knowledge in your team. Data processing agreements under GDPR are part of the standard process.
Do you take on existing systems?: Yes. An assessment of code, dependencies and operations comes first and sets out what is urgent, what is due in the medium term and what effort to expect. You decide on that basis.
Do you work with AI tools?: Yes, where they measurably contribute: in development itself and in client projects where automation or AI-supported workflows are part of the brief. Decisions about architecture and code stay with people, and we agree upfront which tools are permitted in your project.

Working together

Approach and contracts

Technology and data protection

The services behind the answers