Backend work
agencies
can't staff for.
> ONBER.STUDIO :: subcontractor for agencies · Ankara, Turkey · GMT+3
> We are the team a digital agency brings in when a project needs work it can't staff. You win the job and handle design and frontend, then hit the wall: the client's data lives in an on-premise ERP, the workflow needs an internal tool nobody on staff can build, or the whole thing has to end in a correctly formatted PDF.
What we do
> We connect modern web apps to the systems a client already runs: on-premise ERPs, MSSQL and Postgres over ODBC, hosts reachable only through a VPN, syslog and file-drop feeds, internal APIs with no documentation. You get a REST or WebSocket endpoint your frontend can call, and we own everything behind it. Typical case: stock and pricing live in an MSSQL box behind the client's VPN, nobody on the agency side has a route to it, and we ship the sync service plus the documented API on top.
├─ MSSQL · ODBC · Postgres ├─ VPN · syslog · file drops ├─ undocumented internal APIs └─ REST · WebSockets out
> Spreadsheet-and-shared-drive workflows rebuilt as an application. Role-based access so warehouse and finance see different data, an audit trail on every change, search that holds up at real volumes, and structured exports to CSV, XLSX or the next system in the chain. Typical case: order intake runs on one shared XLSX and three chat groups, nobody can say who changed a row or when, and it falls over the week a second branch starts using it.
├─ role-based access ├─ audit trail on every change ├─ search · filters · bulk edit └─ CSV · XLSX · API exports
> Automated workflows whose deliverable is a document, not a webhook. Quotes, invoices, reports, certificates and compliance packets, generated as DOCX or PDF that match the client's template down to the header, the table borders and the page breaks. Moving data between APIs is the easy half. Producing a file the client's accounting team accepts without re-typing it is the half most providers skip, and it is the one we are built around. Typical case: the workflow has to end in a PDF an auditor signs off, generic exports come back rejected for a broken table or a bad page break, and we render from the client's own DOCX template inside the pipeline.
├─ DOCX template → PDF ├─ headers · tables · page breaks ├─ quotes · invoices · certificates └─ stored in MinIO · versioned
Selected work
gozlukcum
- PROJECT
- gozlukcum
- ROLE
- Backend repair
- STATUS
- LIVE DEMO
- URL
- gozluk.onbers.com
> A multi-tenant RFQ platform for opticians. Every RFQ endpoint rejected every request, and the cause was not in the RFQ code. We found it, repaired the flow end to end, then added a sandboxed demo tenant and server-side PDF quotes.
▶ READ THE CASE STUDY
Team
> Python/FastAPI and Node/TypeScript services, PostgreSQL and MSSQL, Docker and Caddy on self-hosted boxes. Writes the adapter layer that has to talk to whatever the client already runs, including the parts with no documentation.
▶ email [email protected]→
> Turns “can you connect this to our ERP” into a spec with a fixed deliverable and a date. Automation pipelines, document generation, and the operational side once it is running in front of a client.
▶ email [email protected]→Stack
hit a wall?
let's talk.
> 20 minutes, technical, straight to the constraint.