Skip to main content
Q-STU· Qomero's software studio

Q-STU · Software Development Studio

Software built around the way your business actually runs.

Custom web apps, internal systems, backends and API integrations. The scope is written down before we build, and delivery is accepted on evidence.

Kovaa's sales team, the ARVUMA store and Synolang all run on software the studio built.

Screenshot of the kovaa.vn homepage
Screenshot of K-LionBook's Today screen, customer data blurred
Screenshot of the despa.qomero.vn homepage

What the studio builds

For each service: what you get, who it suits, and a live build you can compare against.

  • Custom web applications

    A web product with user accounts, plans and payments, or a specialist tool for your own customers.

    You get
    • A written scope: what's in, what's out, and what done looks like.
    • The leanest version that solves the agreed problem.
    • A live release, tried out and checked against results.
    Suits
    Founders who need an MVP with real users; businesses that want to sell a service online.
    Built
    Synolang. One account, one credit balance and one history across Writing and Speaking. When a marking run fails, it says so and takes no credit.
  • Internal systems and dashboards

    Replace spreadsheets with one system the whole team works in: the data in one place, and everyone sees their own part.

    You get
    • A written scope: who uses it, for what, and what done looks like.
    • A system running on your team's real work.
    • Dashboards that read the same data your team enters.
    Suits
    Small and mid-sized businesses running repeat processes on spreadsheets.
    Built
    K-LionBook. Customers, orders, receivables and margins in one place. Kovaa's sales team uses it every day.
  • Backends, APIs and integration

    APIs, server-side data processing and the connections between the systems you already use.

    You get
    • A scope: which system connects to which, what it reads and what it writes.
    • An API or server-side service running in production.
    • Connections tested on real data before anyone relies on them.
    Suits
    Companies that need their tools connected; teams with a server-side backlog and too few people.
    Built
    K-LionBook. Matches customer orders to supplier orders, flags late orders, and reads ad-platform reports in read-only mode.
  • Refactoring and modernising existing software

    We read the codebase you already run, then refactor, extend or rebuild it piece by piece, following the migration plan agreed with you.

    You get
    • An assessment of the current codebase.
    • A scope for what gets refactored, extended or rebuilt.
    • The codebase stays yours; after handover, Qomero can take over running it.
    Suits
    Teams with software in production that has become hard to change or extend.

Who it suits

  • Founders who need an MVP with real users.
  • Small and mid-sized businesses running repeat processes on spreadsheets.
  • Companies that need the systems they use to talk to each other.
  • Teams with a backlog and not enough engineers.

A project fits when

You can say who will use it, what for, and what done looks like. Can't say yet? Making that clear is the studio's first step.

Not a fit

Only need a small company website or a landing page? Q-STU doesn't take that work. Qigital handles this work. Visit Qigital

1. Understand: the problem written down → 2. Scope: a written scope → 3. Build: a test release → 4. Hand over: a release in use

Four steps, in this order

You know what is being built, what isn't, and what done looks like.

  1. Understand. The business problem and the process behind it. We read your spec or whatever documents you have.
  2. Scope. What's in, what's out, what done looks like. Written down, with a quote, before we build.
  3. Build. The leanest version that solves the agreed problem, tried out on real work.
  4. Hand over. Put into real use, results checked against what was agreed, then handed over.

Price and timing depend on the spec, the risks and access to the systems we integrate with. The quote comes once the scope is agreed; there is no fixed price list.

You know which work is really done

Every Qomero project, yours included, runs on Praukron, open source under Apache-2.0: scope, decisions and acceptance evidence in one chronicle. Work reported as done is kept apart from work that has been checked.

Read about Praukron

Technology running in these builds

Only what runs in real products. The technology is chosen for the problem, not the other way round.

  • Web front ends and web apps

    • Next.js · K-LionBook, kovaa.vn, Synolang
    • HTMX · Synolang
    • HTML, JavaScript · ARVUMA
    • TypeScript · K-AutoDesign
  • Servers and APIs

    • Python, FastAPI · Synolang
    • Python · K-AutoDesign
  • Data

    • PostgreSQL, pgvector, Drizzle · K-LionBook
    • Supabase · K-LionBook, Synolang
  • Content and deployment

    • Sanity CMS · kovaa.vn
    • Vercel · kovaa.vn, ARVUMA
  • AI

    • A marking model trained by Qomero · Synolang
    • An image-generation model · K-AutoDesign

This is the technology of each running build, not everything the studio can work with.

Built and running

Running in Qomero's own businesses and products; VietFarmAsia also uses the ARVUMA code under licence. Click a domain to see the live site.

  • 3,179

    registered Synolang users

    Source: Synolang

  • 15

    sellers use K-LionBook every day · Kovaa, internal figure

    Source: Kovaa

  • 63

    provinces with a suitability rating on ARVUMA

    Source: ARVUMA

  • Screenshot of K-LionBook's Today screen, customer data blurred

    Internal system (CRM)

    K-LionBook

    Customers, orders, receivables and margins in one place. Kovaa's sales team uses it every day.

  • K-AutoDesign

    Internal system

    K-AutoDesign

    The customer writes a brief, AI proposes a design, and the quote is tied to one fixed design. In use.

Read the case studies on Qomero

Frequently asked questions

What does it cost?

There is no fixed price list. You get a quote once the scope is agreed, stage by stage, before any work starts.

How long does it take?

It depends on the scope. Milestones are set in the scope document and the contract.

Do you take on existing codebases?

Yes. The studio refactors and modernises software already in production, starting with a read-through of the codebase.

Who owns the code?

You do. The codebase belongs to your business. After handover, Qomero can take over running it if you want.

What if the requirements change midway?

Changes are handled as the contract between us sets out.

Do you deploy to servers?

Yes. The “Hand over” step includes deploying to the live environment.

How do payments and milestones work?

As the contract between us sets out.

Is there maintenance after handover?

Yes, if you need it: after handover, Qomero can take over running the system. Scope and fees follow the contract.

How soon does Q-STU reply?

Within 2 working days of receiving your brief.

Have a software project? Send us the problem or your documents.

A paragraph is enough to start. If you have a spec, designs or a link, paste them in. Q-STU replies within 2 working days.

The form is paused. Your answers are still on the page. Email clients@qomero.vn or call 0917 037 788.

clients@qomero.vn0917 037 788