Cookies

    We use one analytics cookie (Google Analytics) to understand which pages are useful. No ads, no reselling, and declining changes nothing about how the site works. Privacy Policy

    Trust and security

    How we handle your data and run the work.

    For teams that run a vendor review before they sign: how client environments are kept apart, who can write what, how an engagement runs, and what the agreement covers.

    Client data

    Each company sees only its own environment.

    Revuity MCP is the connector that serves a client its own AI Operating Environment inside Claude or ChatGPT. These are the rules it is built to.

    01

    Scoped to your company

    Every read and write a client can reach resolves your company from your authenticated seat, and the data layer enforces that boundary as well as the application.

    02

    Identity comes from the server

    Your company is worked out on the server from your seat. An identifier sent by the client is never trusted to decide what you can see or change.

    03

    Cross-company tests gate release

    Tests that try to read one company's records as another company are a required release criterion for new reads and writes.

    04

    No master key on client paths

    No service-role key sits on any code path a client request can reach. The single exception is the seat invite, which uses it only to add the invited person after checking the caller's role with the caller's own token.

    05

    Internal tools stay internal

    Revuity's internal operating tools are never exposed to clients and never share code with the client-facing connector.

    Sign-in and access

    One sign-in system, and narrow permission to write.

    The connector uses the sign-in system Revuity already runs and keeps its write paths short.

    01

    A single sign-in system

    The connector authenticates through Supabase Auth with OAuth, the same system the rest of the platform uses, and no second user or session system exists beside it.

    02

    Streamable HTTP only

    The connector speaks one transport, Streamable HTTP with JSON-RPC 2.0.

    03

    A short list of writes

    What the connector writes is limited to support and change requests, install progress, content you generate, pending action requests that only a person can approve in the portal, and usage and audit records.

    04

    Your own systems stay yours

    Revuity MCP is never a runtime proxy for your Gmail, HubSpot, Drive, or internal database, so your AI app reaches those directly through your own connections.

    05

    Self-reported state is labeled

    Where a connection or install state comes from what the client reports, the connector says so and does not present it as verified.

    How an engagement runs

    A defined path from understanding to handoff.

    Larger teams ask how the work is run before they ask what it costs, so here is the path.

    01

    Ten steps

    Every engagement moves through Understand, Map, Design, Approve, Build, Validate, Train, Approve Production, Launch, and Handoff, so the work is understood before it is built and validated before it is handed off.

    02

    Scoping before commitment

    Diagnosis is part of qualification and scoping, so you learn what the work involves before you agree to it.

    03

    Three build structures

    Custom application work is scoped as an FDE Blueprint, an FDE Co-Build, or an FDE Build and Deploy, each with its own published price.

    The paper

    What the signed agreement covers.

    Revuity issues a master service agreement with a Schedule A statement of work. The signed document governs, and these are the standing terms it carries.

    01

    Defined scope and written change orders

    No work is performed and no fees are incurred outside Schedule A or a signed change order, and any change to scope, price, deliverables, or timeline needs a written change order signed by both parties.

    02

    You own the deliverables

    Ownership of the deliverables passes to you on receipt of final payment, and each party keeps its own background intellectual property.

    03

    Accounts in your name

    Third-party accounts, cloud resources, domains, and software subscriptions created for the work are set up in your name, and Revuity operates under revocable, limited credentials.

    04

    Confidentiality and personal data

    The agreement carries a duty of confidence, and personal and customer data is processed only on your documented instructions, then returned or destroyed on termination or earlier request, apart from routine backups and legally required copies.

    Plainly

    What we do not claim.

    Revuity does not claim a SOC 2 report, ISO 27001 certification, HIPAA attestation, or any other certification or audit, and makes no uptime SLA, penetration-test statement, data residency promise, or insurance statement on this page.

    If your security review needs something specific, tell us what it is on a call or through the contact form and we will answer plainly about what exists today.

    Start here

    Bring your questions.

    Starter is $299, bought online. For anything your review needs, send a message and we will say what we can show you today.