The site you are reading is new. We rebuilt beysco.com from an empty directory rather than restyling what was there, because the old site had a single job — proving we existed — and that stopped being the job some time ago.
How it is built
It is a Next.js application, statically generated and served from a CDN, in English and Turkish. No page waits on a server to render. Both languages ship as real pages rather than a client-side text swap, which means each one is a URL you can link to and a search engine can index properly.
The two languages were built together rather than bolted on afterwards. English lives at the root and Turkish under a prefix, the URLs are the same in both, and no visitor is redirected somewhere on the basis of a browser setting. Adding a third language later is a file of text and a line of configuration, which is only true because nobody hardcoded a string in a component.
There is no analytics stack watching you read this, no cookie banner, and no third-party script deciding how fast the page loads. Fonts and images were gone through one at a time so the first load holds up on a phone connection rather than only on the machine it was designed on.
Design and build both happened in-house, by the same people who write client code. That was not a cost decision. A studio that outsources its own site is telling you something, and we would rather this be a work sample than a brochure about work samples.
What it is for
The site has one purpose: to explain, without hedging, what we build and how we work. Five services, one process, the people behind them, and a contact route that goes to the engineering team rather than a form nobody reads.
That purpose doubles as the editing rule. If a page cannot survive the question "does this help someone decide whether to work with us", it does not stay. It is why there is no feed of industry predictions here, and why the services pages describe what we actually do rather than listing every technology we could plausibly name. Two pages died that way while the site was being built, and neither is missed.
It will keep changing. Case studies are the obvious gap, and they arrive as clients clear them — the interesting parts of most projects sit under an NDA, which makes this slower than we would like. The news page is the other half of that answer: shorter, more frequent, and ours to publish without asking anyone. Until the case studies land, this is where we write things down.