PHP without frameworks
Daen applications run on PHP written in-house, with routes declared in code, server-side validation and output escaping. There is no framework layer to keep up to date.
Private infrastructure · in-house operation
Dedicated infrastructure for Daen projects.
Our own servers for Daen projects, with isolated execution per application, data kept off the public network and PHP code written by the team that runs the environment.
The path of a request
01
Anycast edge
TLS 1.3 protects the connection and HTTP/3 is served at the edge. WAF, volumetric mitigation and rate limiting filter traffic before it reaches the origin.
02
Restricted origin
The origin does not answer the open internet. It only accepts traffic from the edge. Each application runs in isolation with its own user, session and resource limits.
03
Data and continuity
The database is not exposed to the network, and each application account can only access its own schema. Backups are hash-verified and stored away from the production node.
Development and operations in the same team
Daen writes the applications, ships the releases and maintains the environment where they run. Queries, permissions, capacity and edge rules are decided with the same context. The infrastructure serves those projects only.
Process-level isolation
Each application runs with its own user, session, temporary storage and resource limits. What one project consumes stays within its own limits.
No third parties in the browser
Pages load resources from our own infrastructure only, with no external libraries, fonts or trackers. The single exception is the anti-bot challenge on the contact form.
Verified backups away from the node
Data, files and configuration are copied away from the production node. The SHA-256 check runs before a copy joins the recovery set.
Four areas of infrastructure
Isolated origin, edge protection, data recovery and optional integrations. Anything not finished yet carries the In progress marker.
01
Dedicated servers · isolated execution
Dedicated, restricted origin
Our own servers, sized for Daen projects, with isolated execution for each application. The origin accepts connections from the authorized edge only and keeps secrets outside the public root.
View details
02
Cloudflare · Anycast
Edge termination and filtering
Authoritative DNS on an Anycast network, TLS 1.3 with a minimum of 1.2 and one-year HSTS including subdomains. Edge rules reject known probes and limit bursts on authentication routes.
View details
03
Data and recovery
In progress
Redundancy across providers
Project copies already leave the production node, with an integrity check. Distribution across separate providers is being implemented and will be complete once a restore from the second provider has been tested.
View details
04
Language models · voice · images
In progress
Optional artificial intelligence
Text review, image generation and conversion between text and speech over API, being implemented project by project. Each feature is optional and depends on the client, with the data boundary defined before the first call.
View detailsFeatured articles
DNS, caching, data recovery, cloud, performance and the use of language models, based on technical decisions made for Daen projects.
Performance goes far beyond the server
Origin response time is only one part of the experience. Network, critical resources, images, fonts, JavaScript and visual stability all count.
Artificial intelligence needs context, not magic
Generative models become useful when they receive controlled context, operate within clear boundaries and have their output reviewed before it produces effects.
Cloud without waste: when elasticity pays off
Elasticity creates value when it follows demand. The right choice depends on the workload profile, total cost and the application's ability to scale.