A small studio that builds the whole thing
Korame is a remote-first software engineering studio. We design, build and deploy websites, web applications, full-stack systems and custom software the same people from the data model to the focus ring.
What we actually are
Korame is small on purpose. The work we are good at systems where design, frontend, API and infrastructure decisions have to agree with each other is work that gets worse when it is divided between people who meet at a handoff.
That shape has consequences we would rather state than let you discover. We take on a limited number of projects at a time. We are not the right choice for a programme that needs twelve engineers next month. And there are whole categories of work we turn down, listed further down this page, because taking work you cannot do well is how studios acquire the reputation they deserve.
We are based in India and work remotely with clients across time zones, mostly asynchronously over shared documents and deployed previews, with a regular call in a window that suits you.
How we make decisions
Design and engineering are one job
The same people draw it and build it. That removes the most expensive conversation in this industry the one after a handoff, about what was actually possible.
Budgets, not aspirations
Performance and accessibility targets are agreed at the start and enforced in the pipeline. A target that lives in a proposal is a wish; one checked on every pull request is a constraint.
Boring technology, applied carefully
Nearly every rescue project we take on was made fragile by something being more clever than the problem required. Complexity has to be earned by a requirement, not chosen by preference.
You own everything
Repository, cloud accounts, domain, documentation yours from the first commit. There is no proprietary layer you would have to keep licensing to keep your site running.
We will tell you not to build it
If an off-the-shelf product covers your requirement, or the feature will not pay for itself, that is the advice you get. A project that should not exist is the most expensive kind.
Accessibility is not a phase
Semantic markup, keyboard operability, visible focus and contrast checked against the tokens, done while building. Retrofitted accessibility is always worse and always costs more.
How a project runs
- Step 01
Discovery
Time with the people who will use the thing, including the exceptions they currently handle by hand. Output is a written scope, an architecture and an honest estimate including a recommendation not to proceed if that is the truthful one.
- Step 02
Design system first
Colour, type, spacing, motion and both themes defined as tokens in code before screens are drawn, so the visual language is a system rather than a set of pictures.
- Step 03
Vertical slices
One complete path through the system interface, API, data, deployed before the second one starts. Integration risk surfaces in week one rather than week nine.
- Step 04
Continuous deployment
Every pull request builds, tests and gets a preview URL. Every merge deploys. Releases are small enough to be uninteresting, which is the point.
- Step 05
Handover
Documentation, runbooks and architecture decisions with their reasoning. Continuing without us should always be a live option, not a renegotiation.
What we build with
This is the working set, not a catalogue. If your project needs something outside it, we will say so.
Frontend
- React
- Vite
- JavaScript
- TypeScript
- Tailwind CSS
- Motion
Backend
- Node.js
- REST APIs
- Serverless functions
Data
- PostgreSQL
- SQL Server
- Document stores
Cloud & delivery
- Azure Static Web Apps
- Azure Functions
- GitHub Actions
- CDN & edge caching
Standards
- Core Web Vitals
- WCAG 2.2 AA
- Structured data
- CI/CD
What we do not do
Every studio has a list like this. Most do not publish it.
- Native iOS and Android development we build for the web platform and the APIs behind native clients.
- Azure consultancy for networking, Kubernetes, identity governance or data-platform engineering.
- Paid media, brand strategy or content marketing as standalone services.
- Large enterprise ERP or SAP implementation programmes.
- Anything we would have to learn on your budget without telling you first.
Where a requirement falls outside this, we will say so in the first conversation and point you at the right kind of specialist. That is cheaper for everyone than finding out in month three.
Judge it by the work
Three builds, written up with what was actually engineered rather than what it achieved commercially because we do not publish figures we cannot substantiate.
This site is also part of the evidence. Every route is pre-rendered to static HTML at build time, the artwork is generated rather than downloaded, the fonts are self-hosted and subset, and every animation respects prefers-reduced-motion. The web development page explains why each of those decisions was made.
What we can take on
Work with us
Tell us what you are trying to build and what has to be true for it to be worth building. We answer within a working day.