What we do
Device, access and enterprise policy architecture, security assessment and penetration testing. We begin with workflow discovery, users and project boundaries. Infrastructure constraints, data requirements and operational conditions are documented before implementation.
The agreed scope can include threat model, device policies, access control, event audit, integrations, limitation review, penetration testing and security assessment. Each component has a defined purpose, interface and verifiable output. Technology choices follow the existing environment, operations and the problem.
Integrations document exchange contracts, roles, errors and responsibilities. Data permissions, storage and external-system constraints form part of the delivery plan. Changes are agreed before entering a milestone.
Quality is evaluated through user and technical scenarios. Test reports cover agreed conditions and document limitations. Load evaluation, migration rehearsals and access analysis are scheduled as required by the scope.
Deliverables include software components, permission model, documented limitations. Release preparation includes operations instructions and recovery. Source, documentation and rights follow the contract; maintenance and infrastructure responsibilities are agreed separately.
Pricing depends on scope, effort, integrations, security and timeline. Discovery leads to an estimate or technical proposal by milestone. An initial brief should describe the workflow, current constraints, connected systems and first-release priorities. Current starting prices are listed in the software and service pricing section.
Scope and deliverables
- Threat model
- Device policies
- Access control
- Event audit
- Integrations
- Limitation review
- Penetration testing and security assessment
Pricing and contract
Milestones, estimates and rights are agreed before work begins. Public information is provided in the pricing section.
Software and service pricingFAQ
How does a project start?
With a brief describing the problem, users, constraints and available information. Discussion establishes the discovery scope and next milestone.
Who receives software rights?
Ownership and the assignment or licensing of rights are established by contract. Custom development and licensing can use different terms.