The Cyrillic Font Our CSS Stack Never Reached
Our declared font stack hid an unexpected glyph supplier, so we checked rendered families and kept the historical build fix separate from browser coverage
Reviewed by Dmytro Nasyrov on October 22, 2026.
Our Ukrainian heading had Manrope in its declared font stack. Chromium still drew the letters with an Arial-based fallback. The intended font was available, and its position in the CSS list looked reasonable. Another face answered the request before the browser reached it.
The redesign used Plus Jakarta Sans for Latin text and Manrope for the Cyrillic text it covered. In our historical Next.js build, the generated fallback attached to the first family interrupted that division. We had to inspect the font actually used for a node, rather than accept the computed family list as proof.
The generated face covered more than the intended font
The source family and its fallback did not have identical coverage boundaries. The build generated a metric-matched Arial fallback without a Unicode range restriction. That fallback could supply Cyrillic letters even when the intended first family did not supply the basic Cyrillic glyphs. With that face included in the first font variable, the browser could render Ukrainian before it ever tried Manrope. Merely moving Manrope into the written stack was insufficient: the unexpected face was already inside the earlier variable's expansion.
This distinction matters when diagnosing multilingual typography. A CSS declaration describes candidates. A font download proves that a resource arrived. Neither observation identifies the face that supplied the glyphs of a particular heading.
The recorded fix used two options
For Plus Jakarta Sans we set both fallback: [] and adjustFontFallback: false. The implementation replay records that the latter option alone did not remove the fallback in its Turbopack build. We confirmed the combination against the generated CSS rather than assuming the option name guaranteed the result.
This is a version-bound observation. The current Next.js font reference documents fallback configuration, but it does not turn our recorded build behavior into a promise about every subsequent compiler release. A team upgrading that toolchain should inspect its own generated output.
Removing the generated face also had a cost. While the Latin font loaded, text could fall through to Manrope's fallback, with a different first-paint shift. We accepted that tradeoff for the intended script routing. We did not measure a cumulative layout shift improvement and do not present the change as one.
Sharing the configuration meant checking three copies
The product had separate landing, reader and administration applications. In this setup, putting the font loader in the shared UI package interfered with the compiler and tests importing that package. We retained one app-local font module per application. That was a deliberate duplication boundary. A workspace test checked that the modules stayed identical, while an app test pinned the options responsible for the fallback correction. Moving the code into one shared file would have reduced file count while violating the build boundary we had just verified.
We preloaded the selected Latin and Cyrillic subsets according to the recorded design. That introduced extra font resources on English pages too. The loading choice and the glyph-selection fix were related, but they were not the same claim.
We asked Chromium which fonts it drew
The browser test waited for document.fonts.ready. It then used Chromium's DevTools font report for the Ukrainian heading and the Latin application name. The heading had to include Manrope and exclude Arial or Helvetica; the Latin name had to include Plus Jakarta Sans and exclude Manrope.
| Observation | What it can establish |
|---|---|
| Computed font-family list | The declared candidate order |
| Successful font request | The resource was fetched |
| Rendered-font report for a node | The faces Chromium used for that node |
| Recorded option assertions | The build configuration retained the chosen correction |
These assertions made the failure legible. A test that checked only the CSS family string would have accepted the original defect, because the desired name was already present. The rendered-font report inspected the consequence of the configuration.
Script coverage still had exceptions
The implementation notes identify exceptions for Ukrainian characters Ґ, ґ and the hryvnia sign ₴. In the recorded setup, those glyphs came from the first family's extended Cyrillic subset, while the remaining Cyrillic text used Manrope. Claiming that every Ukrainian glyph came from Manrope would therefore overstate the result.
A single representative heading also cannot certify every possible mixed-script string. The test pinned a concrete product requirement and a known failure. Additional scripts, weights and fallback environments require their own samples.
Evidence scope
The stage-one replay reports successful builds and browser scenarios, and the later redesign merge includes the font work. The test source records the rendered-font assertions described here. Those historical records support the correction in that environment; they do not establish Safari or Firefox behavior. Our most useful change was to make the expected result observable at the glyph supplier. The stack could remain visually persuasive in a code review while the wrong font rendered. A node-level report gave us a regression check that the declaration alone could not supply.
FAQ
Quick answers to common questions about custom software development, pricing, process and technology.
Type to filter questions and answers. Use Topic to narrow the list.
Showing all 14
No matches
Try a different keyword, change the topic or clear filters
-
How long have you been in business?
Pharos Production has been in business since 2013, with over 13 years of experience in custom software development. During this time, we have delivered over 110 applications for 200+ clients across 28 industries, including FinTech, healthcare, crypto and e-commerce. We are rated 5/5 on Clutch based on 107 verified reviews (2026).
-
What services do you provide?
Pharos Production provides six core service categories: AI Development (LLM applications, AI agents, machine learning and computer vision), Blockchain and Web3 (smart contracts, DeFi, tokenization on Ethereum, Solana, TON and other chains), FinTech Development (payment platforms, digital banking, KYC and AML integration), Software Development (mobile apps, web platforms, database design, UI/UX), Security and QA (code audits, penetration testing, smart contract audits, manual and automated testing) and Consulting (architecture design, MVP validation, startup consulting).
-
Where is Pharos Production located?
Pharos Production is headquartered in Las Vegas, Nevada, USA (5348 Vegas Dr, Las Vegas, NV 89108), with an engineering office in Kyiv, Ukraine (44-B Eugene Konovalets Str. Suite 201, Kyiv 01133). We work with clients worldwide and provide remote collaboration across all time zones. Visit our contact page for directions and scheduling options.
-
How big is your team?
Pharos Production has a team of 90+ engineers, including software developers, blockchain specialists, QA engineers, DevOps experts, UI/UX designers, project managers and solution architects. Our founder, Dr. Dmytro Nasyrov, holds a PhD in Artificial Intelligence and leads the technical direction of all projects.
-
What types of customers do you serve?
We serve a wide range of clients, from startups and product companies to mid-sized enterprises and large institutions. Our clients include crypto exchanges, FinTech providers (like Pleenk), healthcare organizations, sportsbook operators (like Pro Gambling), e-commerce platforms and SaaS companies. Pharos Production has worked with 200+ clients across 28 industries since 2013, adapting engagement models to match each client's stage, whether it is MVP validation for a startup or enterprise-scale development for an established business.
-
How is a custom software development company different from an agency?
A custom software development company like Pharos Production assigns one dedicated engineering team that owns your product across multiple release cycles, instead of handing it off once a contract ends. Agencies more often rotate staff between clients and optimize for fast delivery over long-term product ownership.
Pharos Production keeps the same team on your codebase through 2-week sprints, so there is no re-onboarding cost each time you request a new feature.
-
How much does custom software development cost?
Custom software development costs vary based on project scope and complexity. At Pharos Production, typical project ranges are: MVP development ($10,000-$25,000), suitable for startups validating a product idea; full-fledged production ($25,000-$50,000), for established businesses scaling a proven concept; and full-cycle development ($50,000-$80,000+), for complex enterprise-grade systems. These ranges include architecture design, development, QA testing and deployment. Hourly rates range from $50 to $99 depending on role and seniority. Final pricing depends on technology stack, number of integrations and engagement model (staff augmentation, dedicated team or project outsourcing).
-
How long does it take to develop a custom software application?
Development timelines depend on scope and complexity. At Pharos Production, a typical MVP takes 2-4 months, a production-ready application takes 4-8 months and a complex enterprise system can take 8-12+ months. We use an agile methodology with 2-week sprints, delivering working increments after each sprint. Every sprint includes a retrospective, progress report and planning session for the next iteration. This approach ensures transparency and allows businesses to launch faster by prioritizing high-impact features first. Get a timeline estimate for your project.
-
What industries does Pharos Production serve?
Pharos Production serves 28 industries: FinTech, MiCA Compliance, Banking, Insurance, Crypto, Healthcare, Fitness, E-Commerce, Food & Restaurant, On-Demand, Manufacturing, Automotive, Energy, Oil & Gas, Supply Chain, Construction, Real Estate, Gaming, Streaming, Media, Telecom, Education, Aviation, Travel, Logistics, Marketing, Agriculture and Recommender Systems. Our deepest expertise is in FinTech, blockchain and healthcare, where we have delivered compliance-ready platforms (HIPAA, PCI DSS, GDPR) and high-load systems handling thousands of concurrent users. For the latest industry insights, read our guides on FinTech trends in 2026 and the Web3 technology stack.
-
Why hire a software development company instead of building in-house?
Hiring a software development company offers faster time-to-market, lower upfront costs and access to specialized expertise without long-term employment commitments. According to Deloitte's 2024 Global Outsourcing Survey, 57% of companies outsource software development to access skills they cannot hire internally.
Factor In-house team Software development company Time to assemble 3-6 months (recruiting + onboarding) 1-2 weeks Upfront cost High (salaries, benefits, equipment) Lower (project-based pricing) Specialized expertise Limited to who you can hire locally Access to 90+ engineers across blockchain, AI, FinTech Scalability Slow (each new hire takes months) Fast (scale up or down per sprint) Long-term commitment Full-time employment contracts Flexible engagement models Risk High if key engineers leave Company ensures continuity and knowledge transfer For businesses that need blockchain, AI or high-load architecture expertise, outsourcing to a specialized firm like Pharos Production reduces risk and accelerates delivery.
-
What projects does Pharos Production not take on?
Pharos Production focuses on mid-to-large custom software projects with budgets starting at $10,000. We do not take on template-based websites, WordPress theme customization or short-term contracts under one month. We also do not provide non-technical staffing (marketing, sales or design-only roles). Our strongest fit is blockchain, FinTech and healthcare projects where security, compliance and high-load architecture are critical. For smaller projects or MVPs under $10,000, we recommend exploring freelance platforms or no-code tools as a more cost-effective starting point.
-
Why does Pharos Production use agile methodology?
We use agile with 2-week sprints because it reduces the risk of building features that miss the mark. Each sprint ends with a working demo, a retrospective and a plan for the next iteration.
This means clients see progress every 14 days and can adjust priorities based on real results, not assumptions. We chose this approach after years of experience showing that rigid, fixed-scope contracts lead to scope creep, missed deadlines and products that do not match market needs by launch day.
-
When should you NOT hire a custom software development company?
Custom development is not the right choice in every situation. You should not hire a custom software company if: your problem is fully solved by an existing SaaS product (e.g. Shopify for e-commerce, Salesforce for CRM); your budget is under $10,000 and timeline is under 4 weeks; you need a simple landing page or marketing website (WordPress or Webflow is faster and cheaper); or you are still validating the idea and have not spoken to potential users yet.
In these cases, off-the-shelf tools or no-code platforms offer better ROI. Custom development makes sense when you need unique workflows, regulatory compliance, high-load architecture or competitive differentiation that packaged software cannot provide.
-
What kind of projects has Pharos Production delivered?
Here are three anonymized examples from our recent delivery history:
FinTech startup - payment platform (MVP)
Scope: mobile app + backend API with bank-grade encryption. Team: 4 engineers, 1 QA. Timeline: 10 weeks. Budget: $38,000. Result: launched on schedule, processed $2M+ in transactions within the first quarter.Healthcare provider - patient portal (Full product)
Scope: HIPAA-aligned web platform with EHR integration, appointment scheduling and telemedicine. Team: 6 engineers, 1 DevOps, 2 QA. Timeline: 6 months. Budget: $120,000. Result: 15,000+ active patients, zero compliance violations in two annual audits.Crypto exchange - trading engine (Complex)
Scope: high-load matching engine handling 50,000+ orders per second, multi-chain wallet infrastructure on Ethereum and Solana. Team: 8 engineers, 2 QA, 1 security auditor. Timeline: 11 months. Budget: $340,000. Result: 99.97% uptime, passed three independent security audits.See more projects: NoMoreBets, Pulse, Sagas, Gambit Stream and Pleenk. For the full portfolio, visit our case studies. Learn more about the technology behind these projects in our guide to stablecoins and crypto infrastructure.
Stas Rysin is the Lead Frontend Developer at Pharos Production. His work covers the design system, reader interfaces and administration workflows of a professional learning platform for aesthetic medicine.
