Three Frontend Apps, One Runtime Configuration Boundary

Reviewed by Dmytro Nasyrov on October 22, 2026.

Our initial frontend architecture separated the public landing application, the reader chat and the administration console. Because they served different audiences and deployment domains, treating them as one browser bundle would have made those boundaries harder to keep explicit.

I participated in that initial architecture as well as the later redesign. This case describes the September design decisions and their subsequent integration boundaries. It distinguishes a recorded architectural requirement from evidence that every acceptance condition had already been exercised.

Three applications did not mean three copies of everything

A shared UI package was intended for components used by at least two applications, while domain-specific components stayed with their owning application. That rule made reuse follow actual consumers rather than moving every new component into a shared package preemptively. The threshold was a design criterion, not a claim that every shared file had been independently audited against a permanent count. Later work still exposed build-specific exceptions, including font configuration that remained app-local with parity tests.

Deployment addressing belonged on the server

The initial design prohibited putting backend addresses in public environment variables because the intended route went from the browser to its own application origin and from that server boundary to the upstream service. A built image could receive upstream addresses at runtime, separating the release artifact from the environment where it ran and making the gateway responsible for the relevant service and identity integration without asking the browser to know internal deployment addresses. Hiding a hostname did not by itself establish proxy security. Permission checks and accepted-operation rules still belong in the actual request path. Later backend-mode work made those routing boundaries more explicit and removed permissive prototype fallbacks.

Revisit assumptions as real services arrive

The September architecture preceded the staged migration of profile, bookmarks, Library and reports. Its demo-era behavior should not be presented as the final data ownership model. Later integration records show which adapters were temporary and which service contracts replaced them.

Rendering and middleware rationale also belonged to that historical design. A design decision made for the pinned framework and build setup is not automatically current advice for another version. The stable question is which runtime boundary the product needs; the mechanism implementing it must be checked in the target release.

The request boundary can be reviewed without internal addresses

Browser requests in the initial design went to the application's own /api/graphql and /api/chat/stream paths. At the server boundary, the upstream address was resolved and the relevant token attached from the session. That upstream service address did not need to become a browser configuration value.

browser
  -> current application's /api/graphql or /api/chat/stream
  -> application server's runtime upstream configuration
  -> owning service

built release image + environment-specific server configuration

This is a redacted decision diagram, not a captured production request. Its useful question is where an environment change is consumed. If the upstream address is embedded in a public build variable, changing it may require rebuilding the browser artifact. In the recorded design, the server consumes it at runtime so the release image can remain the same across environments.

That design does not make every proxy request safe, and the presence of a server route does not establish its permissions. Later work still needed operation allowlists, session handling and correct ownership of profile and bookmark requests. The initial diagram describes the addressing boundary; the later adapters determine what the boundary actually permits.

Sharing followed consumers and release consequences

The source's two-consumer rule gives a concrete extraction review. A base control used in the reader and console can belong in shared UI. A source-review workspace used only by administration can stay with that application even if another interface may eventually want something similar. Shared configuration and translated catalogs can have their own consumers without moving every domain component into the same package.

Separate applications also carried a release requirement: changing administration should not restart the reader application, and public delivery should not serve the administration bundle. Those are intended consequences of the split, not measured bundle-size or deployment-isolation results. A real release check must inspect which workloads and assets actually change.

The later app-local font exception shows why this record needed room for amendments. Reuse could still mean matching behavior and parity assertions when a build-specific module could not be placed in the common location. Keeping that exception explicit was more useful than declaring that all shared concerns had exactly one physical file.

Architecture criteria need observable gates

Build, health and environment checks appeared as initial acceptance criteria describing what the architecture intended to protect. A planned gate is not a receipt that a particular deployment passed it. Later merged frontend work supplies concrete examples: matching app-local font modules, a runtime-gated gallery and explicit backend-mode imports. Those examples help review the original boundaries without inventing a single blanket architecture-success measurement.

What belongs in a reusable architecture record

The table above records the audiences, ownership and runtime configuration boundary without exposing internal addresses. It should be paired with the actual release's build and request evidence when assessing a deployment.

We did not record an independent bundle-size, cost or delivery-speed comparison for the original split. Its value here is a traceable set of decisions that later feature work could either preserve or deliberately revise.

FAQ

Last updated: October 22, 2026

Quick answers to common questions about custom software development, pricing, process and technology.

Expand all Collapse all

Search FAQs

Type to filter questions and answers. Use Topic to narrow the list.

Showing all 14

• How long have you been in business?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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.