AI that can be audited
Models work on your documents and data with logged sources, access control and a person who approves the result.
For companies where software must pass IT, security and procurement reviews: AI in business processes, secure Laravel/PHP applications, integrations with enterprise ERP and support agreements with clear response times.
Models work on your documents and data with logged sources, access control and a person who approves the result.
Roles, audit logs, dependency scanning and security testing are part of the scope, not an add-on before go-live.
NDA, data processing agreement, copyright transfer, architecture documentation and answers to vendor security questionnaires.
Document search with sources (RAG), data extraction from offers, tenders and invoices, ticket classification and draft answers. We built this in our own product TenderIQ: tender document analysis and an AI bid plan.
Security audit against OWASP ASVS, dependency and secret scanning, role and permission review, audit logs, hardening of deployment and coordination with your penetration testers.
Under NIS2 essential and important entities must manage the security of their suppliers. We deliver what they need from a software vendor: incident procedures, logs, access control, update policy and documentation.
Single sign-on with Microsoft Entra ID or another SAML/OIDC provider, integrations with SAP, Comarch ERP XL and internal APIs, queues and monitoring.
Response times agreed per priority, monitoring, backups with restore tests, release windows and runbooks your team can use without us.
We deploy to your cloud tenant or on-premise servers, through your CI/CD. Code and documentation belong to you after each stage.
Data classification, threat model and the list of controls are agreed with your security team before development starts.
Separate test and production environments, least-privilege access for our team and access you can revoke at any time.
Architecture, data flows, list of personal data processed, dependency inventory (SBOM) and incident procedure.
A named technical lead, a fixed demo rhythm and decisions recorded in the backlog, so nothing depends on one person’s memory.
1–2 weeks: process, systems, data, risks and the controls the solution must meet.
A narrow scope (for example one AI use case or one integration) on real data, evaluated against agreed criteria.
Staged releases through your CI/CD, with tests, code review and demos every 1–2 weeks.
Documentation, runbooks, training and a support agreement with response times per priority.
Only if you agree to it. We can use models hosted in the EU, a provider under a data processing agreement or an open-source model on your infrastructure. The choice is made per use case after a data review.
Yes. NDA, data processing agreement (GDPR art. 28) and copyright transfer to the code are standard parts of our contracts.
We prepare the software side: logs, access control, update and incident procedures and supplier documentation. Legal assessment and the formal audit are done by your compliance team or an external auditor.
Yes. We deploy to your cloud tenant or on-premise servers and work through your CI/CD, repositories and access policies.
A 1–2 week discovery and security review, or a proof of value for one AI use case or integration. Both end with a written scope, estimate and risk list.
Start with a 1–2 week discovery and security review. You get a written scope, estimate and risk list.
#software
No noise. Real systems. Software that runs in production.
Talk about the project