Assurance

Security, access
and operating
responsibility.

We take responsibility for the software lifecycle, with client-controlled deployment, agreed access and ongoing support.

Standards & evidence

SOC 2 Type II
and ISO 27001.

Our SOC 2 Type II report and ISO 27001 certificate for Ever Quint Technologies Private Limited are available on request. Review the covered services, period and scope for your engagement.

  • AICPA SOC 2 badge
  • ISO 27001 badge

Discuss the evidence relevant to your engagement:

  • Covered entity
  • Services assessed
  • Applicable period
  • Assessment scope
How delivery works

Your cloud.

  1. Client-controlled deployment

    We deploy client implementations in the client’s AWS, Azure or Google Cloud environment. The client owns the deployment and data.

  2. Client-approved access

    We identify the permissions required and work with the client’s system owners. They provision OAuth applications, API access or scoped warehouse users for the integration.

  3. Delivered code and dependencies

    The client owns delivered implementation code. During scoping, we review the ownership and licence terms that apply to existing platforms, customised forks and open-source dependencies.

Our software
responsibility.

We handle ideation, design and software implementation. The engagement defines support, ownership and migration responsibilities.

  1. Workflow and usability

    We deliver software against the agreed requirements, following EverQuint’s engineering standards and the standards agreed with the client. If usability prevents people from completing the intended work, we revisit the workflow, design and implementation.

  2. In-app support

    Users report bugs, feedback and feature requests in the application. We prioritise by severity. For application-wide outages, we begin investigating immediately, 24/7. Support coverage and commitments are agreed for each engagement.

  3. Migration responsibility

    When a client chooses an agreed platform upgrade, we carry out the migration and ask the client team to verify the result.

AI workflow evaluation

Test sources,tools andapproval rules.

For an AI workflow, identify which sources it can use, which tools it can call and which actions need approval.

Test its answers and failure cases against the proposed task.

Before an engagement

Security and delivery questions.

Discuss these points in your security, technical and procurement review.

Our SOC 2 Type II report and ISO 27001 certificate are available on request. We identify the entity, covered services and period relevant to your engagement.

Assurance evidence applies to the entity, systems, services and period assessed. Check those boundaries for the product you are evaluating.

Client implementations run in the client’s cloud. Support coverage, response commitments and operating responsibilities are agreed for the engagement. Our Perkins&Will work is governed by a master services agreement and yearly statements of work.

We can customise an existing EverQuint platform, including a client-specific fork, when it fits the requirement. Pricing, licensing, integration and delivery responsibilities are defined in the engagement terms.

You can engage our engineers without adopting an EverQuint platform. We consider a product when it fits the workflow and existing systems.

The client leads organisational adoption and business change. We remain responsible for delivering and supporting software against the agreed requirements, including addressing usability problems that prevent the intended work.

We hand over the repositories and documentation reviewed by our team and AI tools. The delivered implementation code, deployment and data remain with the client.

Tell us about the workflow, current systems, people, constraints and the change you need. We can then scope a review or engineering engagement.

Work with EverQuint

Discuss an
application
or integration.