Kriyonix

We take on your product like it's our own.

Kriyonix is a small software studio. We design and build web applications, backends and practical AI features for founders and businesses. We build products of our own too, so we know what it means to live with the result.

Talk through your project See what we've built

What we can build for you.

Start with the problem you have. The technology comes second, and we'll explain it as we go.

Web applications

A first version people can use

You have an idea, a spec, or a process you can describe. We turn it into a web application real users can sign in to, and make the product calls with you: what to build first and what can wait.

  • TypeScript
  • React
  • Next.js

The web apps for both our products are built this way.

Backends and automation

Systems that replace manual work

The backend is the logic and data behind an application: where information lives, who can see it, and what happens on its own, like alerts, reminders and scheduled jobs.

  • Python
  • FastAPI
  • Node.js
  • PostgreSQL

KemonChilo chases unanswered cases on its own and keeps an audit trail of every step.

APIs and integrations

Your tools, connected

APIs let separate pieces of software exchange data. We build them, and connect your systems to the services you already use, so information moves without copy and paste.

  • REST APIs
  • Webhooks
  • Telegram bots

JossJobs reads job boards on Greenhouse, Ashby and Lever. KemonChilo alerts managers on Telegram.

AI features

AI where it earns its place

Language models are good at reading messy text: emails, documents, postings. We use them for that, check what they produce, and keep decisions that must be right in plain code. If AI isn't worth the cost, we'll say so.

  • Anthropic Claude
  • Extraction
  • Evaluation

JossJobs uses Claude to pull facts from job postings, and every fact has to quote its source.

Services and technology

Our own products.

Owning a product means living with every decision: what each AI call costs, which edge cases break, what users actually need. Both are pre-launch. The demos run in your browser, so try them.

Job-search intelligence, for people seeking remote work

JossJobs

Reads international remote job postings and tells you which ones you could realistically be hired for, quoting the posting's own words as proof.

  • The AI reads each posting once, and every user reuses the result
  • Eligibility is decided by rules, not guessed by a model
  • Says "uncertain" instead of making something up
How JossJobs works
Pre-launch
Senior Backend Engineer, Remote
We hire across EMEA and APAC time zones. This is a full-time role, employed through our EOR partner, and needs at least 4 hours of overlap with UTC+1. Python and Postgres experience preferred.

Tap a fact to see the sentence it came from.

Service recovery, for restaurants in Bangladesh

KemonChilo

A QR code on the table asks guests how it went. A low rating reaches the manager on Telegram while the guest is still seated, so it gets fixed before anyone walks out.

  • No app, login or phone number for guests
  • Alerts an escalation contact if nobody responds within 10 minutes
  • The guest confirms whether they were actually helped
How KemonChilo works
Preparing a restaurant pilot
Table 7
How was your experience?
Tap a star.
Manager's Telegram
No alerts. All tables are happy.

Try a low rating, then a high one.

Next in the studio

Your product

An idea, a manual workflow, or a half-built thing that needs finishing. We'll build it with the same care as our own, and stay on after launch if you want us to.

Talk through your project
This space is saved for you.

How a project runs.

Six steps, in this order, whether the product is ours or yours.

  1. Understand

    The problem, the people it's for, and what can't go wrong. We'll question assumptions, including ours.

  2. Shape

    What the first version includes, what waits, and how it's built. Agreed before code, and written down.

  3. Build

    Design and engineering in small working pieces, so you see the product take shape as it does.

  4. Verify

    Tests for the parts that must be right: the edge cases, the failure paths, the numbers.

  5. Launch

    Ship it, with what's needed to run it in production.

  6. Improve

    Real usage, not assumptions, decides what comes next.

We build software we have to live with.

Software isn't finished when it ships. It has to keep working for the people who use it, keep making sense for the business, and stay easy to change. Building our own products keeps that in front of us. Here's what it looks like in practice.

Decisions get written down.

We decide what to build and why before writing code, and record it. JossJobs has 47 decision records, so nobody has to guess later why it works the way it does.

What must be right gets tested.

JossJobs has over 1,000 backend tests. KemonChilo's tests run against a real database on every change.

AI has to earn its cost.

JossJobs reads each job posting once and reuses the answer for every user instead of paying for it again. KemonChilo uses no AI, because it doesn't need any.

Kriyonix is founder-led. Rabbil Yasar Sajal started it after seven years building Python backends, the last five on a small remote UK team building Issuebear and TourAmigo.

The company is early. The standard isn't.