Versioning and review
Code is managed under version control and reviewable branches. Where a repository has automated tests or CI, those gates form part of release; where it does not, equivalent validation must be defined before deployment.
Engineering & Security
Operational software needs control after the code works.
We treat changes, data, releases, AI and recovery as part of the product. The exact controls depend on criticality, architecture and project requirements; we do not use a generic checklist to imply compliance that was never agreed.
How we reduce risk
Controls that fit the operation.
Not every product needs the same amount of process. A small internal tool and a critical platform should not carry the same control cost, but both need an explicit way to change without improvisation.
Environments and releases
We separate development from production and avoid using production servers as development workspaces. Material releases are tied to an identifiable revision with validation and evidence of the version actually operating.
Rollback and continuity
Application and infrastructure changes should include backup, rollback or an appropriate reversal path. After changes, health and critical-flow checks are performed according to the system.
Secrets and configuration
Credentials, tokens and sensitive configuration stay out of public artifacts and source where they do not belong. Exact separation depends on hosting and architecture.
Data and artificial intelligence
AI does not remove responsibility for data.
Choosing a model is an architecture and risk decision, not only a response-quality decision.
01
Use AI where it earns its place
We prefer deterministic rules for behavior that must remain predictable and models for work where classification, extraction, assistance or language adds value.
02
Data according to sensitivity
We do not assume every provider or model is appropriate for confidential information. Provider, retention, location, access and local/cloud deployment are evaluated against project requirements and available contractual guarantees.
03
Human in the loop
When an action can affect money, access, sensitive information or an important decision, we design human approval, traceability or autonomy limits according to risk.
Working with organizations
Security is also a contractual conversation.
When a project requires it, we can review NDA terms, data processing, access controls, hosting, backups, SLA requirements, security questionnaires and provider restrictions before architecture and scope are finalized.
NDA and confidentiality
Confidentiality obligations can be structured around the engagement and the information involved.
Privacy and processing
Controller, processor and provider roles are documented according to the actual data flow and applicable contract.
SLA and support
Availability, response times and support are not assumed: they are defined and priced according to criticality and required capacity.
Technology ecosystem
Softentgroup is a member of NVIDIA Inception. Membership is an ecosystem signal and access point to resources for AI startups; it is not presented as a security certification, product certification or endorsement of a specific customer project.
Transparency
What this page does and does not claim.
Is this equivalent to a certification?
No. These are engineering practices and criteria. Softentgroup does not present this page as an ISO, SOC or other external certification.
Does every project use exactly the same controls?
No. Controls are adjusted to data, criticality, architecture, budget and engagement obligations.
Can you answer a security questionnaire?
Yes, when it is part of evaluation. Answers are based on the real project design and selected providers.
Does AI always run in public cloud?
Not necessarily. The technical option depends on the case; enterprise cloud, managed services or local models can be evaluated when requirements justify them.
Next step
If security or continuity is part of the problem, it belongs in scope from the beginning.
Tell us what system, data and restrictions are involved. That changes architecture, delivery and cost, and it is better to know before we build.