[Platform and security]

Plugs into the systems your firm already runs.

Send contracts in from any system with one request. Get signed events back when a review finishes or a signature lands. And know exactly where your contract text goes, because we tell you.

Book a demo How we handle your data
Your system sends a contractPOST

          
Clausel replies201 Created

          

            
            

          

        

        

          
Webhook deliveries to your endpoint

          

        

      

      

    

  







  

    

      

        
[Infrastructure]

        
Every system, every layer, and which way the data moves.

      

      
Your systems sit at the edge. Clausel's five layers sit in the middle. Each connector carries its honest level: built in, a ready template, a one-way feed, the open API, or planned.

    

    
    
      
  • Built in, needs setup
    • 
      
  • Ready template
    • 
      
  • One-way feed
    • 
      
  • Open API, your keys
    • 
      
  • Planned
    • 
    

    

      

      
    
        
        
  • 
          
          Google Workspace
          Gmail, Drive, Calendar
          Built in, an admin sets it up
          
    Gmail, Drive and Calendar read into a chat. Each person switches them on in the chat that needs them, and nowhere else. A firm admin sets the connector up once.
    
          
        
    • 
        
  • 
          
          Outlook mailBeta
          Microsoft 365, MCP route
          Built in, Microsoft sign-in
          
    Mail read through the Microsoft 365 MCP route. Each person signs in with Microsoft. Needs a Microsoft client, secret and tenant from your admin.
    
          
        
    • 
        
  • 
          
          HubSpot
          Deal to draft, and back
          Ready template
          
    A HubSpot deal starts a draft, and the signed contract goes back to HubSpot. Two ready workflow templates with a shipped spec. Needs a private-app token.
    
          
        
    • 
        
  • 
          
          Salesforce
          Closed Won to draft
          Ready template, event only
          
    A Closed Won opportunity starts a draft. Clausel receives the event only. Nothing is written back to Salesforce.
    
          
        
    • 
        
  • 
          
          Your own systems
          Ingestion API
          Open API, your keys
          
    A practice system, a document store or a script posts a contract as text or a file. Clausel files it on the record, reads its details and checks it before the reply.
    
          
        
    • 
        
  • 
          
          Microsoft 365 files and mail
          SharePoint, OneDrive, Outlook intake
          Planned
          
    Planned, not built today. Files and mail from Microsoft 365 are on the roadmap, with no date promised.
    
          
        
    • 
      


      

        

          [Clausel]
          
Hover a system or a layer to see which way its data moves, and what it needs.

        

        

          Work
          
DraftAnalyseRedlineApproveSignKeepRenew

          
Seven stages on one contract record. Calendars pull their deadlines from here, your endpoint receives its signed events from here, and signing is native with a sealed certificate.

        

        

          Control
          
Playbook and rules engineGrounding and quote checksConsistency engineHuman approval gatesHow we test the AI 

          
Answers are checked against the document before you see them. Reads from an outside system run freely. Anything that would change an outside system waits for a person.

        

        

          Associates
          
Deep agentSub-agents when a crew is definedSelf-improvement where enabled42 SkillsSealed sandbox no networkWorkflows 36 blocks, 31 templates, 5 triggersMCP client per deployment

          
The deep agent plans, uses tools and works through steps. Specialist sub-agents join when a crew is defined. An Associate can propose a change that is tested first and kept only if the score rises, where enabled. The MCP client reaches approved outside tools through an open standard, configured per deployment.

        

        

          Knowledge
          
Contract recordHybrid search keyword, then pgvectorEmbeddings on Clausel's serversOCR vision model, scansSection scout long documents

          
One record per contract. Search runs keyword first, then pgvector meaning search with embeddings computed on Clausel's own servers. Scans go through OCR with a vision model. Long documents are handled by a section scout and chunked search.

        

        

          Models
          
OpenAIAnthropicGoogle GeminiOne vendor setting per deploymentDifferent models per taskFailover and web search optional, needs setup

          
Contract text goes to the vendor set for the deployment, one setting for every model call. Different tasks can use different models. The answer comes back through Control before you see it. A backup vendor and web search are optional and need setup.

        

        
Access
Email sign-in. OpenID Connect and SAML by configuration. Roles: admin, lawyer, viewer. Connector secrets encrypted.

      


      
    
        
        
  • 
          
          Calendars
          Google, Outlook, Apple: .ics feed
          One-way feed
          
    Your calendar subscribes to the deadlines feed and pulls every date from the record. Nothing comes back.
    
          
        
    • 
        
  • 
          
          Your endpoint
          Signed webhooks, 8 events
          Open API, your keys
          
    Eight events, each signed with HMAC over the timestamp and the body, three attempts, and a delivery log you can read.
    
          
        
    • 
        
  • 
          
          Word add-in
          .docx export works today
          Planned
          
    Planned, not built today. A redline already exports as a Word .docx with native tracked changes.
    
          
        
    • 
        
  • 
          
          Slack, Microsoft Teams
          Incoming webhook
          One-way feed, no sign-in
          
    Paste an incoming webhook and a workflow posts the events you choose to a channel. No app to install, no sign-in. Nothing comes back.
    
          
        
    • 
        
  • 
          
          SAP, Oracle, Workday, ServiceNow
          Any REST API, 50 actions
          Open API, your keys
          
    Through the open API: an admin registers an OpenAPI spec and a service credential, which is encrypted and never shown again. Reads run freely. Every other method waits for a person. Up to 50 actions.
    
          
        
    • 
        
  • 
          
          DocuSign
          Clausel signs natively
          Not connected
          
    No connector. Clausel signs natively and seals a certificate on the signed document, so nothing leaves for a signing service.
    
          
        
    • 
      

    

    
Levels say what is built today. Planned means not built yet, with no date promised. A logo means Clausel connects to that system, nothing more. Where your contract text goes is set out in plain words under security.

  







  

    

      

        
[How we test]

        
Tests that can fail, and say so.

        
Legal AI you can prove needs tests that can fail. These are ours. Each one guards against a mistake a lawyer would feel, and the bench shows what a pass and a stop look like.

        
In a demo, we can run a review of your own contracts and go through the results with you.

        
    
          
  • Recorded reviews and contracts with planted problems live in the code, beside the product.
    • 
          
  • Checks that need a model are run on demand. The rest are plain code, with no model in the loop.
    • 
          
  • No test replaces a lawyer's judgement. A stop is shown on the screen, never hidden.
    • 
        

      

      

        

          Clause 3.2, an example
          
Renews unless a party gives 30 days' notice before the term ends.

          
        

        
    
          
  1. Every change points at words that are in the contract.Clause 3.2, found word for word. A quote the document does not contain is refused.
    2. 
          
  2. The same question asked two ways reaches the same document."The Helios notice period" and "how long before the renewal" both open clause 3.2. A name that is not on file is not invented.
    3. 
          
  3. A contract with planted problems is reviewed and marked against the answer key.A notice period shorter than the playbook's position: found, and quoted.
    4. 
          
  4. An answer is marked only when the judge quotes the words it relied on.The judge quoted "gives 30 days' notice". The quote was checked against the answer and found.
    5. 
          
  5. A change that cannot find its words is not placed.Not placed. The proposed wording quoted "thirty days". The contract says 30 days'. The change is listed to place by hand.
    6. 
          
  6. A redline leaves as Word tracked changes, each marked as Clausel's.Insertions and deletions in the Word file carry the author Clausel, so Word shows them as changes to accept or reject.
    7. 
        

        
Showing the checks on an exampleAn illustration. One check stopped a change and said so.

      

    

  







  

    

      
Connectors that stay off until you want them.

      
A firm admin connects Google Workspace once. Each person then switches Gmail, Drive or Calendar on in the chat that needs it, and nowhere else. Outlook mail comes through the Microsoft 365 route, in Beta, with each person's own Microsoft sign-in.

      
    
        
  • Your accounts and the firm's connectors, listed apart
    • 
        
  • Every role can see the Connectors page. Keys, webhooks and open API actions are for admins
    • 
        
  • Web research is optional and needs setup
    • 
      

    

    

      

        Connectors
        
          
          
        
      

      

      

        
In this chat

        

          
          
          
        

        
No connectors are on in this chat. Clausel cannot see your inbox, files or calendar here.

      

    

  







  

    

      
One request puts a contract in Clausel.

      
Your practice management system, a document store or a script can push a contract as text or as a PDF, Word or text file. Clausel files it, reads its details and runs a consistency check before it replies. No model is involved in that first check.

    

    

      

        
Keys for your firm
Each key starts with clsk_, belongs to your firm, is shown once and can be revoked.

        
Safe to retry
Send an Idempotency-Key. The same key within 24 hours returns the original contract's id and makes no copy.

        
Text or a file
JSON with the contract text, or a PDF, Word or text file of up to 30 MB.

        
Checked on arrival
The reply carries the contract type, the governing law and a count of proven internal defects by severity.

        
Starts workflows
A workflow waiting for new contracts starts at once, and the reply lists its runs.

        
Documented
An OpenAPI 3.1 description your developers can load straight into their tools.

      

      

        
New ingestion key

        
For: Practice management sync

        

        
Copy this key now. Clausel keeps only a fingerprint, so you won't be able to see it again.

        
      

    

  







  

    

      
Signed events when something happens.

      
Subscribe an endpoint to the events you care about. Every delivery is signed with your secret over the timestamp and the body, so your endpoint can reject a captured request that is replayed later.

    

    

      

        

          
contract.ingestedA contract arrived through the API

          
review.completedA review finished, with its findings

          
signature.sentA document went out for signature

          
signature.completedEvery signer has signed

          
signature.requirementA signer uploaded or confirmed a required document

          
changes.requestedA signer asked for changes instead of signing

          
rule.firedA firm rule that is enforcing took action

          
workflow.stepA workflow step delivered its result

        

        
    
          
  • Three attempts per delivery, and a delivery log you can read
    • 
          
  • An endpoint that keeps failing is paused, and the pause is shown
    • 
          
  • Rotate the secret with 24 hours where both old and new signatures are sent
    • 
          
  • Endpoints on internal network addresses are refused
    • 
        

      

      

        

          
          
          
        

        

          

          

          

        

      

    

  







  

    

      
Where your contract text goes, in plain words.

      
Legal teams ask us this first, so here is the straight answer. Search embeddings are computed on Clausel's own servers. Contract text still goes to the AI vendor set for the deployment when a model reads or drafts, and what comes back is checked against your document before you see it.

    

    

      

        
Embeddings computed here
Clause search uses embeddings computed on Clausel's own servers. Contract text goes to the AI vendor only when a model reads or drafts.

        
Checked before you see it
Figures in an answer are checked against the document, and quotes the document does not contain are caught.

        
Scoped to your firm
Repository reads, keys and webhooks all belong to one firm and stay there.

        
Connector secrets encrypted
Credentials for systems you connect, and keys for open API actions, are encrypted and never shown again after you save them.

        
A person approves
Reads from an outside system run freely. Anything that would change an outside system waits for a person.

        
Sign-in and roles
Email sign-in is on. OpenID Connect and SAML are available by configuration. Roles: admin, lawyer, viewer.

      

      

        

          
One model vendor setting for the deployment

          
One setting moves every model call between three AI vendors. Different tasks can use different models from that vendor. A backup vendor and web search are optional and need setup.

          
CLAUSEL_PROVIDER=openai

          
            
            
            
          
        

      

    

      

      
The algorithms, by name.

      
Signed webhooksHMAC-SHA-256
Signed over the timestamp and the body, so your endpoint can verify each event.
Signed contractsSHA-256
A fingerprint over the document, computed before the certificate is added.
Connector tokensAES-256-GCM
Encrypted before they are stored, and never shown again.
API keysSHA-256
Shown once. Clausel keeps only the hash, so it cannot show the key again.
Guest linksSHA-256
Clausel keeps only the hash of each one-time link.
Passwordsbcrypt
Salted and hashed. Clausel never stores the password itself.
In transitHTTPS
TLS with certificates renewed automatically.

    

  







  

    

      
Hosted by us, scoped to your firm.

      
Clausel runs as one deployment that we operate. Every record, key and webhook carries your firm, and reads stay inside it. If you need a deployment of your own, talk to us and we will scope it with you.

      Talk to us about your own deployment
      
Files you can use, not just answers

      
When a task needs a file, Clausel builds it in a sealed sandbox with no network and hands it back to download.

      
Board summary.docxDeal update.pptx

    

    

      
Your firmRepository, playbooks, keys, webhooks

      
ClauselReview, drafting, rules, workflows, signing

      
SearchEmbeddings computed on our servers

      
AI vendorOne setting for the whole deploymentOpenAIAnthropicGemini

    

  







  

    
[See how it wires in.]

    

      
We'll walk your developers through an ingestion key and a signed webhook in a demo.

      

        Book a demo
        Next: review and redline