Skip to content
Kiremt

Software built by engineers in Addis Ababa, for teams everywhere.

Kiremt is a software company based in Addis Ababa. We design and build web platforms, mobile apps, SaaS products and applied AI systems — from first sketch to a production team you can call at 3 a.m.

design. build. ship. repeat. 24/7 support from the engineers who built it
kiremt.com — delivery live

Systems in production

97.9% uptime, trailing 12 months

10+

Remote teams

Across Addis Ababa and Bahir Dar

2

Solutions provided

1

Median time to first release

From paid discovery kickoff

6 wks

Current stack

GoReactPostgresRedisPython

1

Solutions provided

2026

Founded

Addis Ababa, Ethiopia

43

Trained Professionals

Across nine disciplines

10+

Products shipped

Production systems in use

98%

Client retention

Trailing 12 months

What we do

Four pillars of service, one team

Most projects draw on more than one of these. An MVP might be three weeks of web development, two of design and a standing analytics retainer. An AI feature usually lands as an automation wrapped in a service.

All services
02

Outsourcing

Extend your team with senior engineers, designers and QA. We plug into your repo, your standups and your release calendar.

03

AI solutions

Applied AI that clears the bar in production. Retrieval over your own data, evaluations before launch, and a clear line between what the model does and what the code guarantees.

04

Developer training

Train your engineers in Go, React, Vue and Nuxt. We run workshops, code reviews and mentoring programs that leave your team more capable than they were before.

Our team

Nine disciplines

We staff a project with the people it actually needs rather than a fixed crew. Every Kiremt project has an engineer, a designer and a QA engineer on it — not as an upsell, but because the alternative is shipping twice.

9

Software engineers

Go, Python and TypeScript across backend and platform.

6

Full stack developers

Own a feature from schema to interface.

5

Frontend developers

React, Vue and Nuxt, obsessed with Core Web Vitals.

5

Backend developers

Go services, Postgres schemas, reliable queues.

4

UI/UX designers

Research, interface design and design systems.

4

Data scientists

Analytics engineering, forecasting, applied ML.

4

QA engineers

Test automation and release quality gates.

3

Project managers

Delivery, scope and the awkward budget conversation.

3

Business analysts

Requirements, process maps and acceptance criteria.

Our tech stack

Boring where it counts, modern where it helps

We pick tools we can support at 3 a.m. and defend in a code review. The stack below is not a religion — it is what we have run in production, on our own products and on client systems.

Boring by default

Postgres as the source of truth, one transactional store, explicit consistency models.

Go for services

Concurrency and small binaries. Our backend services are predictable to operate.

Typed where it pays

TypeScript on the front end so a refactor is a compiler run, not a support ticket.

Redis and Elasticsearch

Cache and search derived from Postgres, never as a second source of truth.

Primary stack

GoPythonJavaScriptTypeScriptReactNode.jsVueNuxtPostgresElasticsearchRedis

Also in regular use: Docker, GitHub Actions, Terraform, Prometheus, Grafana, Sentry, Playwright and Vitest.

Solutions delivered

Products we took from idea to production

Two of our own products, built by the same teams that work on client projects. Both run the stack on the right.

All solutions

Clients and partners

We have worked with teams across manufacturing, logistics, agriculture, marketing, education and the public sector — building the systems they run their days on.

B Brtat
H Hype Ethiopia
Q Quantum Vibe
E Ethio Pets
M Maya Engineering
M Mina Shop
C Catalyist Creatives

Let's build together

Tell us what you are building. We will tell you honestly whether we are the right team for it.

Send a paragraph about the problem. You will get a reply from an engineer, not a form letter, within one business day. If we are not the right fit, we will usually know someone who is.

Start the conversationReplies within one business day

What happens next

  1. 1 We reply with initial questions, a rough range and whether we are the right fit.
  2. 2 A call or a workshop with the engineers who would actually do the work.
  3. 3 A paid discovery phase produces a written scope and a number we can stand behind.