Skip to main content
    TRLog in (opens in a new tab)
    Vekilaw logo: Hukuk Bilgi İletişim Sistemi (legal information and communication system)

    A firm's working day sets our direction.

    Vekilaw is built to run a law firm's day. Six principles guide every product decision we make.

    Illustrative image of a team reviewing a product flow
    Illustrative teamwork
    01/03DirectionWho we are →

    Our mission

    To let law firms run their case, client, document, calendar and finance work securely and traceably. To take the lawyer's time away from administration and give it back to legal work, while keeping the firm's data inside its own boundaries, making every action traceable and always leaving the final decision to a person.

    Our vision

    A profession in which a law firm of any size in Turkey runs its daily work with a simple interface and confidence, and software is an ordinary, trusted part of legal practice. A solo practice and a legal department with several teams should get the same data protection, the same deadline accuracy and the same simple workspace.

    How we measure success

    By daily behaviour, not promises: was the deadline calculated correctly, did the payment close correctly, did an unauthorised record become visible? We look at these questions through tests and the feedback in support requests; if the answer is no, we fix that first.

    02/03Six principles

    Six principles stand behind every decision

    Product goals and conditions requiring clarification before service begins are described below.

    1. 01/06

      Real behaviour, proven by tests

      Feature availability, setup conditions and acceptance status are described within their scope. UYAP and e-signature connections are in preparation.

      Real acceptance status for critical behaviour is tracked separately.

    2. 02/06

      Data isolation is the default

      Each firm's data is separated per company. Isolation is not a setting added later, it is the foundation of the product.

      Access is restricted by company, branch, case and permission scope.

    3. 03/06

      Transparent pricing

      Check prices, limits, periods and applicable service conditions before payment. The pricing page uses validated catalogue information and identifies unavailable information.

      Plan scope and prices are displayed when the current catalogue is validated.

    4. 04/06

      Focus on Turkish legal practice

      Cases, clients, documents, calendars and finance are the product focus. Deadline calculations require lawyer review; payment and e-document operations depend on provider setup and acceptance.

      Deadline calculations are reviewed by a lawyer alongside the circumstances of the case.

    5. 05/06

      Accessibility

      The interface is offered in Turkish and English. Keyboard access, visible focus and readable contrast are design goals. Mobile distribution and usage conditions require confirmation before service begins.

      Keyboard, focus and contrast acceptance is verified through real interface checks.

    6. 06/06

      Human review

      AI drafts and never decides. Whether it is a petition or a client message, the last word and the responsibility stay with the lawyer.

      AI output is offered as a draft and left to the lawyer's approval.

    03/03Working approach

    How do we approach quality and security?

    Vekilaw is developed and operated by Vekilaw. ISO/TSE certificate details have not been published.

    • QualityQuality managementWe aim to make workflows, issue records and correction results traceable.
    • SecurityInformation securityData access is restricted by role, branch and case permissions; operational conditions are reviewed before service begins.
    • ServiceService managementSupport, change and maintenance procedures are clarified alongside service conditions.
    • ContinuityBusiness continuityOutage communication, backup and recovery targets and drill results require confirmation before service begins.
    • DevelopmentSoftware life cycleWe aim to make development traceable through requirements, code review and test records.
    • ProductProduct qualityCriteria such as functionality, performance, security, usability and maintainability feed into product decisions.
    • ImprovementProcess assessmentProcess maturity or independent assessment results require confirmation through published evidence.
    • Certificate statusCertificationVerified certificate details have not yet been published on this page.

    We do not publish certification claims without verifying the certificate number, scope and validity. See the security page for product features and the technology page for infrastructure.