# Web software your teams and customers sign in to every day. > Custom web applications for customer portals, internal tools and B2B platforms: role-based access, integrations, CI/CD and a monitored production rollout. Source: https://www.algofact.tech/en/services/solution-engineering/web-application-development Language: en-US Updated: 2026-10-26 Languages: en-US, tr-TR ALGOFACT builds custom web applications: customer and dealer portals, internal operations tools and B2B platforms where people sign in, create records and approve work. We do not build brochure sites. Projects start with business analysis, the architecture is agreed in writing, releases ship in short cycles you can test, and go-live comes with access control, monitoring and runbooks. Engineering runs from our offices in Adana and Ankara TEKMER under ISO 27001:2022, for clients in Türkiye and the United States. ## Key facts - **What we build:** Portals, internal tools, partner platforms - **Access model:** Roles, organizations and single sign-on - **Connects to:** ERP, CRM and existing databases - **Hosting:** AWS, Azure, GCP or your own servers - **Information security:** ISO 27001:2022 - **Ownership:** Code, access and runbooks stay with you ## When is a custom web application worth building? Buy before you build. If an off-the-shelf SaaS product covers most of your process, configuring it is usually faster and cheaper, and we will tell you so. A custom application makes sense when the process itself is part of how you compete, when several systems have to come together on one screen, or when per-seat licensing and customization of a packaged tool will cost more over the years than owning the software. The symptoms are familiar. Data gets copied by hand between spreadsheets, email and two different systems. Partners phone in to ask about an order or an application. The monthly management report takes several people days to assemble. A well-designed web application puts that data in one place and ties every step to a record and a named user. What this service is not: template marketing sites and campaign landing pages. The focus is software in which authenticated users do real work. ## Typical applications Most of what we build falls into one of these shapes, and many projects combine two or three. ### Customer and dealer portals Customers or dealers check their own orders, applications, documents and status from their own accounts. Data is scoped by organization, so each user sees only what belongs to their company. ### Internal operations tools Admin panels that replace a process run on spreadsheets and email. The family health center management software and the queue management system for migrant health centers built for Türkiye’s Ministry of Health (Sağlık Bakanlığı) are examples. ### Single-operation management systems Applications that run one operation end to end: exam center management for Akademi Deneme, security systems management for the Zonguldak Governorship, storage hangar management for Ohalo and model management for GAP Photo Studio. ### Multi-company platforms Supplier, distributor or partner platforms where several companies work in the same system, with organization-level permissions, approval chains and reporting. ### Data and reporting workspaces Screens that pull scattered data into one filterable, exportable view for managers, with the query behind every figure kept traceable. ## How the project runs ### Discovery and screen inventory We list user roles, what each role does and the spreadsheets, forms and systems in use today. Scope is written as a list of screens and business rules, not as a slogan. ### Clickable prototype Critical flows are prototyped and walked through with real users before any code is written. A misunderstood screen costs minutes to fix at this stage. ### Architecture and data model We settle the data model, integration points, authentication method and hosting. If an integration looks risky, a short proof of concept comes first. ### Release cycles The application is built in short cycles, each ending with a version you use on a staging environment. Automated tests and code review run on every change. ### Go-live and handover Data migration, user training, monitoring and backups at go-live. Runbooks go to your team, and an optional embedded team can keep building after the first release. ## Architecture, access and security In business applications the hard security problem is usually authorization rather than encryption: who may see and change which record. If that is not modeled from day one, it is expensive to retrofit. We build role and organization scoping into the data model, write sensitive actions to an audit log and connect to your identity provider (Microsoft Entra ID, Google Workspace, Okta or another SAML or OpenID Connect provider) for single sign-on. We pick technology your team can run after we step back. That typically means widely used open-source components such as PostgreSQL, containerized deployment on AWS, Azure, GCP, Kubernetes or your own servers, dependency scanning in the pipeline and code review against the OWASP Top 10. Where personal data is processed, GDPR and KVKK requirements are handled at design time. ## Working with an engineering team in Türkiye Engineering runs from Adana and Ankara TEKMER, and the US entity, Algofact Software and Technology Inc., is based in Dover, Delaware. Türkiye stays on UTC+3 all year, which overlaps with most of the European working day and with mornings on the US East Coast. Discovery, sprint reviews and demos run over video calls; on-site visits are planned case by case during discovery. ## What you receive ### Scope document and prototype Roles, screens and business rules, plus the prototype everyone signed off on. ### The running application With separate test, staging and production environments and an admin panel. ### Integrations and API Connections to your existing systems and a documented API other applications can use. ### Repository and CI/CD pipeline Source code, automated tests, the deployment pipeline and environment configuration. ### Runbooks and user guides How to operate the application, restore from backup and onboard new users. ## Questions ### What is the difference between a web application and a website? A website presents information to visitors. In a web application people sign in, create records, approve work and generate data, which calls for a permission model, database design, integrations and monitoring. This service covers only the second kind. ### Can you migrate data from spreadsheets and our legacy system? Yes. Migration is planned as its own work item: fields are mapped, cleansing rules are written, a trial migration runs on staging and you check the results with us. The production migration happens only after that check passes. ### Will the application work on phones and tablets? Screens are responsive by design. If you need the camera, offline use or push notifications, a mobile app is worth considering as well, and both clients would share the same API. ### Do we own the code? Yes. The repository, cloud accounts and runbooks sit with you, and the details are set out in the project contract. ### What drives the timeline and cost? The number of user roles and screens, how complex the business rules are, which systems the application must connect to and how much data has to move. After the discovery call we split the scope into phases and present a written plan and estimate for the first release. ## Related - [Solution Engineering](https://www.algofact.tech/en/services/solution-engineering) - [Mobile app development](https://www.algofact.tech/en/services/solution-engineering/mobile-app-development) - [ERP, CRM and HIS integration](https://www.algofact.tech/en/services/solution-engineering/erp-crm-integration) - [Use cases](https://www.algofact.tech/en/work) - [Discovery call](https://www.algofact.tech/en/contact)