INTRANET.CO

Software as a Service is dead.Long live Software as a Service.

AI has revolutionized how software can be delivered. Drop your SaaS vendors for your own bespoke internal network of applications.

Try the demo

$2,000 / organization / monthUnlimited seats, unlimited usage

+
Your infrastructure

CRM · Team wiki · Photo app

INTRANET
manifest.tsIntegration code
Business database 
return context.data.transaction({
  database: "organization",
  run: ({ tx }) => tx.query({
    sql:
      "SELECT id, name " +
      "FROM products WHERE id = ?",
    params: [input.id],
  }),
});
External services 
export async function exportProduct({
  input, context,
}: OperationArgs<{
  id: string;
  name: string;
}>) {
  return context.connectors.erp
    .products.update(input);
}
Select a building block to see its code.

How INTRANET works.

  1. One trusted way in.

    Employees sign in through your trusted company login. Once inside INTRANET, every app, company dataset, and business operation is available to them.

  2. Define your business in code.

    Provision your business data, operations, and connections in one code-defined contract. Our concierge team helps you get it right, with onboarding and ongoing support included.

  3. Your code becomes your APIs.

    INTRANET compiles your contract into a runtime server and SDK. Applications get the building blocks. Your team decides what to build.

    • Data
    • Operations
    • AI
    • Connectors
    • Files
    • Realtime subscriptions
    • Identity
    • App hosting

  4. Your infrastructure. Our care.

    We deploy and manage INTRANET on your own infrastructure. Your databases and credential store run in your environment.

  5. Employees ship their apps.

    Build with AI or write the code. Publish HTML, CSS, and JavaScript to INTRANET, ready for the whole company to use.

    Time management

    Track team hours, review timesheets, and keep project schedules in sync.

Build your own
Airtable.

The workflows you need. Built for your company.

$2,000/ organization / month

Unlimited seats, unlimited usage

Try the demo

Managed plan. We deploy and manage your intranet.

What problem does this solve?

Building an internal app is getting easier. Giving every app a database, access to business systems, and a place to run still creates work. We’re building a shared backend and app host so employees can build useful tools without each maintaining their own infrastructure.

What’s in the demo?

A sample INTRANET you can explore for yourself. See how company apps, shared data, and AI work together.

Do we have to replace our existing tools?

Start with one app. INTRANET can connect to the systems you already use, so you can build around them at your own pace.

Where does an app save its own data?

The proposed runtime manages named SQLite databases for app-specific data: shift requests, project notes, approval status, or whatever your workflow needs. An author can import a database with its schema and initial records, then read and write through the shared SDK. Publishing an updated app preserves its live data. Employees don’t need to deploy a separate database server for each app.

Can app data connect to our business data?

Yes. The design supports server-side joins between app databases and business data managed by the runtime. A shift-planning app could connect its requests to shared team and location records, without downloading everything into the browser. Data in external systems is accessed through connectors; it doesn’t automatically become a local table. Changes to primary business records go through your defined business operations.

How does this fit with AI app builders and MCP?

Use your preferred coding tool to create the app. The proposed runtime gives that app a consistent home for business operations, persistent data, files, and AI calls. Connecting a model to a tool is one part of the workflow; the finished app still needs somewhere to run and save shared state. Authors publish ordinary HTML, CSS, and JavaScript that use the runtime’s APIs.

Is this an integration framework or an app catalog?

Integration is part of it. The core is a shared backend that apps actually run against, with business logic, managed data, and hosting in one place. A catalog helps people find existing tools; connectors reach existing systems. Neither alone provides the common runtime for those tools. General workflow orchestration is outside the initial scope.

Who sets up the backend, and who builds the apps?

Your technical team defines the shared business data, operations, and integrations in one organization contract. We compile that into the runtime and API definitions. Employees build apps against those capabilities, adding app-specific data as needed. New shared business behavior goes through a contract change, so every app doesn’t have to reimplement the same rules.

Who can access the apps and data?

Each intranet is a trust boundary. In the initial design, everyone authenticated to its runtime can access all published apps, data, and operations, and can publish apps themselves. Named app databases organize data; they aren’t private to an app or its author. Credentials stay on the server, but there are no per-user or per-app permissions within an intranet.

What if a team needs more restricted access?

Spin up a separate intranet for that group. For example, a finance team can have its own intranet with access limited to its members and its own data, apps, and integrations. Everyone admitted to that intranet still shares the same capabilities. Set the boundary around the people who should have access to everything inside it; use separate intranets when those groups differ.

Do we still need testing and production environments?

Yes. AI can help write and update software, but changes still need validation. The design separates development and production data and credentials, checks compatibility when publishing apps, and uses reviewed change plans for runtime and database changes. Updating an app’s files is separate from migrating its data. Rolling back code does not undo a database migration.

Does this solve app sprawl, cost, and quality?

A common backend reduces repeated infrastructure and gives teams shared capabilities to reuse. The proposal also includes usage metering, quotas, logs, and release history. Teams still need to decide which apps are worth building, who maintains them, and when to retire them. App testing, support expectations, and reliability targets remain work to define and verify for each use case.

Do you have a cheaper plan?

Yes. The self-managed plan is $1,000 per organization per month, half the price of the $2,000 managed plan. Your team handles deployment and ongoing operations. Support is not included.

Can we get a fully managed plan with an on-call engineer?

Yes. The fully managed plan is $10,000 per organization per month and includes an on-call platform engineer, in addition to the deployment and management included in the $2,000 managed plan.