Skip to content

About us

Since 2016 we have been designing, building and maintaining software, first as Code Town, and since 2023 as Digital Templars. The same company, the same principles.

Company history

From Code Town to Digital Templars

We started in 2016 as Code Town. In 2023 the company took the name Digital Templars, with the same registration numbers and the same principle: build things that keep working for longer than a year.

  1. 2016

    Code Town and the first large projects

    Under the name Code Town we build BarterKey, an exchange platform for local businesses, modular .NET Core, SQL Server and an API ready for a mobile app.

  2. 2020

    Gepard Biznesu

    We receive the Gepard Biznesu 2020 award for business achievement.

  3. 2023

    A new name: Digital Templars

    Code Town sp. z o.o. changes its name to Digital Templars sp. z o.o. The company, its registration numbers and its registered office stay the same.

  4. 2024

    The end of the Excel era at a rail operator

    We complete the first phase of a system that replaced spreadsheets for route planning, train driver rostering and reporting, on time and within the agreed budget.

  5. 2026

    Impact’26 in Poznań

    We take part in the Impact’26 congress, one of the most important business and technology events in Central and Eastern Europe.

Illustration: a Templar banner with pennants on a mast
2016first projects, back then as Code Town
17companies and institutions among our clients
3offices: Bystra, Bielsko-Biała and Jelenia Góra
Illustration: Templars loading a ship in harbour
Team

A team matched to your project

We start by understanding your business. On that basis we form a team of the right technology experts, developers, designers and project managers, so that it fits the specification and the goals.

Close collaboration, not a black box

We work closely with your team, and you talk directly to the people who write your system. We regularly show working parts of the system, so you can follow progress as it happens.

Skills matched to the stage

Analysis calls for a different line-up than the build, and the build for a different one than maintenance. The team changes along with the project, documentation and code reviews provide continuity.

Illustration: two crossed banners with a seal and scrolls
See for yourself

Don’t take our word for it, see our deployments and reviews

Our portfolio shows what we have built and under what conditions. References are our clients’ own words about what working with us was like.

Illustration: a scroll of references with a row of wax seals
What guides us

Four principles we stick to

They come from our terms of collaboration and apply to every project, from the first conversation to maintenance.

We say “we won’t do that”

The initial conversation ends with an honest answer on whether we are the right partner, even if that means no contract.

The code is yours

For custom-built systems we transfer the economic copyright, the source code and the documentation. We don’t build dependence on us.

Estimate before work

We write down the scope before we start, and a change of scope is a deliberate decision by both sides, no surprises on the invoice.

Maintenance is not an add-on

After launch we move to an agreed level of support, from handling individual tickets to a full SLA with response times.