Services
Four kinds of work, the same ones behind our own products. Each starts with the problem it solves; the technology is there to back it up, not to lead the pitch.
What we build
Web applications
A first version people can use
Most projects start before there's a codebase: a rough idea, a spec, or a process you can describe but haven't built. We turn it into a web application real users can sign in to.
We make the product calls with you along the way: what the first version needs, what can wait, and where a simpler approach does the same job.
Both our products' web apps. See how KemonChilo went from guest flow to manager alerts.
Backends and automation
Systems that replace manual work
The backend is the part of an application you don't see: where data lives, who can see what, and what happens without anyone clicking a button, like alerts, reminders and scheduled jobs.
We design data models, authentication, background workers and notifications for the edge cases a real product meets, not only the happy path a demo needs.
KemonChilo's worker chases unanswered cases on its own, and every step is kept on an append-only audit trail.
APIs and integrations
Your tools, connected
An API is how one piece of software talks to another. If your team copies data between systems by hand, an integration can do it instead, reliably and on time.
We build APIs for your own products, and connect them to the services you already rely on through their APIs and webhooks.
JossJobs pulls postings from Greenhouse, Ashby and Lever. KemonChilo delivers alerts through Telegram.
AI features
AI where it earns its place
Language models are good at reading unstructured text and pulling out what matters: extraction, classification, ranking, drafting. We use them for that, and check what they produce against the source.
Decisions that must be right stay in plain, testable code. Every model call is a cost, so we cache what can be reused, and we'll tell you when AI isn't worth it.
The discipline behind JossJobs: Claude extracts, rules decide, and each posting is read once for every user.
What we build with
The tools behind our own products, so we know them in production. We choose per project, for what the product needs.
- Frontend
- Backend
- Data
- AI
- Integrations
- Testing and delivery
Cloud infrastructure and native mobile aren't listed, because Kriyonix doesn't have shipped work to show for them yet. The founder's earlier production work ran on AWS; see About.