Teams & On-Premise Self-Hosting

Team collaboration is free on md-log's hosted SaaS for up to 5 members. md-log On-Premise is a fully self-hosted deployment for when you need a team larger than 5 members, or when your AI work reports, images, and annotations must stay inside your own firewall instead of an outside cloud. Start with a free team, then move the same product in-house when you need to.

What On-Premise is

md-log On-Premise is a fully self-hosted deployment where you run the entire md-log product inside your own infrastructure. The AI agent's work reports, attached images, stylus annotations, and version history all live in your own storage behind your firewall — not an outside cloud. It's the same product as the free SaaS for individuals; only the location of your data changes.

You don't need On-Premise just to work as a team. Team collaboration is free on the hosted SaaS, for up to 5 members — sign in and you can create a team and share reports right away (team collaboration). On-Premise is the option for two cases — (1) when you need a team larger than 5 members (unlimited seats), and (2) when the IP inside those reports must stay behind your firewall. Adoption runs through a sales conversation on the contact page.

Why On-Premise

Work reports written by an AI coding agent carry your company's code context and decisions — in other words, your intellectual property. And a free team is capped at 5 members. If either of the following is true, On-Premise is the answer.

  • When you need more members. To go beyond the free 5-member cap — bigger teams or unlimited seats — you scale out with On-Premise.
  • When data must stay in-house. Work reports, images, and annotations all stay in storage you control and never leave the organization.
  • Run it behind your firewall. You own authentication, storage, and backups, and every save piles up as an immutable version, so your AI-collaboration history becomes an onboarding asset that stays inside the organization.

For what md-log is and how the review loop works, see the overview and review & annotation docs.

What you'll run (overview)

You run the On-Premise deployment inside your own infrastructure — an application server plus your own data storage (documents and metadata, images, and ink data) — with authentication, storage, and backups all under your control.

  • Reports, images, and annotations stay only in your storage. Nothing goes to an outside cloud.
  • No public inbound required. It's set up to run behind your firewall without opening any inbound ports from the outside.
  • Authentication, storage, and backups are operated by your organization.

The specific components and requirements (server sizing, deployment method, and so on) are covered during the adoption conversation.

Migrating from a free team to On-Premise

Already collaborating with a free team? When you need more than 5 members or your data must stay in-house, you move the same product to On-Premise. For how free team collaboration works, see the team collaboration doc.

Most teams start light on the free SaaS. Sign up at app.md-log.com, create a team of up to 5 members, and share reports to collaborate. Connect your agent by minting your MCP key yourself in Settings → Tokens (see the MCP connection guide).

When the moment comes where you need more seats or you decide "our IP must stay in-house," you move to On-Premise. The workflow and features you already use stay the same; the data simply comes inside your own infrastructure. If you're still evaluating, walk through the quickstart first to feel the flow.

Account security options

The same account-security features are available in an On-Premise environment.

  • Optional two-factor authentication (TOTP): login 2FA using an authenticator app plus recovery codes. When enabled, it protects login even if a password leaks. 2FA gates web and mobile login only — MCP/PAT keys are exempt.
  • Document-scoped MCP keys: the MCP key an agent uses is scoped to document operations, so a key alone can't change your password, mint other keys, or manage login sessions. If a key leaks, revoke it in Settings → Tokens and mint a new one.

How to adopt

On-Premise adoption runs through a sales conversation, and pricing is by inquiry.

  1. Leave your team size and requirements on the contact page.
  2. Work through deployment and rollout together.
  3. Deploy to your own infrastructure and run the same workflow behind your firewall.

For further questions, email support@md-log.com. Common questions are answered in the FAQ.

Frequently asked questions

Do we need On-Premise to collaborate as a team?

No. Team collaboration is free on the hosted SaaS for up to 5 members. On-Premise is for when you need a team larger than 5 members or your data must stay in-house.

What's included in On-Premise?

On-Premise is a fully self-hosted deployment of the entire md-log product that you run in your own infrastructure. The application server and data storage both live inside your infrastructure, so reports, images, and annotations stay only in your own storage, and your organization runs authentication, storage, and backups. The specific components are covered during the adoption conversation.

Can we migrate from a free team to On-Premise?

Yes. Most teams collaborate as a free team of up to 5 members first, then move the same product to On-Premise once they need more seats or decide their IP must stay in-house. The workflow and features stay the same; only the data comes inside your own infrastructure.

Where is our data stored?

With On-Premise, your work reports, images, stylus annotations, and version history are all stored in your own storage behind your firewall. Nothing goes to an outside cloud, and your organization runs authentication, storage, and backups itself.

How much does On-Premise cost?

On-Premise pricing is by inquiry. Leave your team size and requirements on the contact page and the sales team will walk through adoption and rollout with you.

Does On-Premise need public internet access?

No public inbound is required. It's set up to run behind your firewall without opening any inbound ports from the outside.