Inkspect

Deeply
intelligent
code review.

Every line. Worth a second look.
Understands the context. Catches what matters.

Start with Cloud See it in action

Open source. Use our cloud or host it yourself.

api/projects/delete.tsSample review
06const user = await requireUser(req);
07const { projectId } = await req.json();
08 
09await db.project.delete({
10 where: { id: projectId }
11});
Sessionuser.id
Ownershipproject.ownerId
Connected. Not checked.
InkspectSecurityjust now

A valid session. But whose project?

This user is authenticated, but ownership is never checked. Someone else’s project could be deleted.

Context considered1 meaningful finding
A little ink. A deeper look.

Less to sift through.
More worth your attention.

Context before comments A reason for every finding The final call is yours

Good review starts
with understanding.

A diff tells you what changed. The surrounding code tells you what it means. Inkspect connects the two, giving you findings grounded in context and suggestions you can act on.

Take a closer look
A little ink.
A lot of clarity.

Meet your second pair of eyes

The details make
the difference.

Some issues look perfectly fine at first glance.
Pick an example. See what a closer look reveals.

InkspectOpenExample changes · 3 filesInteractive example

Ask Inkspect

Understand the code behind the change.

Selected fileapi/projects/delete.ts

A question is a good place to start.

Explore the example code, understand a finding, or see why a suggested change matters.

Interactive demo with prepared answers from 3 example files. No live AI connection.

The missing permission checkSecurity review
api/projects/delete.ts−3+5
OriginalSuggested change
export async function removeProject(req: Request) {  const user = await requireUser(req);  const { projectId } = await req.json();   const project = await db.project.findUnique({    where: { id: projectId },  });  await db.project.delete({ where: { id: projectId } });    return Response.json({ deleted: true });}
export async function removeProject(req: Request) {  const user = await requireUser(req);  const { projectId } = await req.json();   const result = await db.project.deleteMany({    where: { id: projectId, ownerId: user.id },  });  if (result.count === 0) {    return new Response(null, { status: 404 });  }  return Response.json({ deleted: true });}
01

The missing permission check

Scope the delete to both the project ID and the current owner. Return 404 when no matching project exists.

api/projects/delete.ts
Security1 finding
Comparing original and suggested code
0 of 3 files viewedIllustrative review. Changes stay in this example.

From pull request to perspective

A natural part
of your pull request.

Stay in the flow. Keep the context.
Make the decision with a clearer picture.

01 / Open

Your code, your workflow.

Connect your repository and open a pull request. Inkspect brings the review directly to the conversation your team is already having.

02 / Understand

Read beyond the diff.

Inkspect retrieves related code and follows the questions that emerge during review, connecting the change to the context behind it.

03 / Decide

Merge with perspective.

Get a clear explanation and a practical suggestion. You choose what changes and what ships.

Explore how Inkspect reviews

Context for your whole team

One codebase.
Human and AI teammates.

Help a new teammate find their way around the project. Give an AI assistant the context behind its next task. Both use the same retrieval layer.

Ask the codebase. Learn the project.

A new developer joins your team and opens the dashboard. They can ask how authentication works, where a feature lives, or why a module behaves a certain way. RAG retrieves relevant code and documentation to ground each answer in the project.

Dashboard conversation · illustrative example

Where should I check workspace access for an invoice?

Check workspace membership before returning the invoice. A signed-in session alone does not grant access to its workspace.

Retrieved contextdocs/access-policy.mdsrc/auth/membership.ts

A starting point for onboarding, with source references to explore.

Pull context into your AI workflow.

Describe the task to the CLI context pull tool. Retrieve the relevant code, conventions, and documentation, then pass that context to your AI assistant alongside the prompt. The assistant gets a focused starting point without loading the whole codebase into every prompt.

CLI context pull · illustrative workflow
Your task
Add a workspace access check to invoice reads.
Retrieved context
Invoice handler, membership helper, access policy.
AI handoff
Your prompt + relevant snippets + source references.

The same project knowledge, ready for an AI teammate.

Retrieval stays within repository permissions. Missing context should be made explicit; indexing and targeted follow-up reads may still be needed.

Explore team context

Open source.
Your choice of home.

Let us run Inkspect for you, or run it on your own infrastructure. Choose what fits your team.

Managed by us

Inkspect Cloud

Get straight to the review. We take care of hosting and updates, so your team can focus on the code.

  • No infrastructure to maintain
  • Updates managed by Inkspect
  • Your pull request workflow
Start with Cloud Explore Inkspect Cloud
Managed by you

Self-hosted

Make Inkspect part of your own infrastructure. Set the boundaries, manage access, and update on your schedule.

  • Your deployment environment
  • Your access and retention policies
  • Open source you can inspect and adapt
Explore self-hosting Compare your options

The code deserves a second look. Ours, too.

Why open source

A name with a point of view

Made of ink.
Driven by attention.

Ink leaves a mark. Inspection gives it meaning.

Inkspect brings the two together. A name for the care that goes into reading code, understanding a decision, and noticing what might have slipped past.

Our drop is the act of making. The eye inside is the attention we give it. Because a good review starts with respect for the code, and the person who wrote it.

Every line deserves a second look.

A few things to know

Before the
first review.

Cloud or self-hosted: which should I choose?

Choose Inkspect Cloud to leave hosting and updates to us. Self-host if your team wants to run Inkspect on its own infrastructure and manage access, retention, and updates. Compare the two options.

Is Inkspect open source?

Yes. Inkspect is an open-source code review product, with a managed cloud option and a self-hosted option. Read about our approach.

How does Inkspect fit into my workflow?

Sign in to Inkspect Cloud or your own instance, connect your repository, and open a pull request. Inkspect adds contextual findings and suggestions to your review, so your team can discuss them where the work happens.

Will Inkspect replace a human reviewer?

Inkspect gives reviewers useful context and an extra set of eyes. Your team keeps ownership of the decisions, the changes, and the merge.

What does Inkspect look for?

Issues that can change how your code behaves: missing permission checks, unhandled failures, concurrency problems, and other logic or security risks. Each finding explains what matters and why.

Does Inkspect change or merge my code?

Inkspect provides findings and suggested changes. Your team reviews the reasoning, runs its checks, and decides what to apply and merge.

Give your code
a second look.

Start with Cloud

Prefer your own infrastructure? Explore self-hosting.