What are you trying to get done?

Six jobs a small team has to get done, and what each one actually looks like here.

Run the office week

The unglamorous half of every business: what we decided, who is doing what, what is on this week, where the file went. It is nobody’s job in particular, so it happens badly or not at all.

Decisions that stay decided

Written down where the decision happened, so the reasoning is still there when someone asks in six months.

Documents · Chat

Work with the reason attached

A task carries the context it came from, so picking one up does not start with a meeting.

Tasks

One calendar, one drive

Meetings, deadlines and files in the same place as the work, reachable by people and agents alike.

Calendar · Drive

The part nobody chases

Follow-ups become dated tasks, created by an agent that was in the conversation. The bit of a job that slips is the bit that depends on someone remembering.

Tasks · Calendar

Any of this works with a team of one. Three seats are free and one of them can be an agent, which is what makes a team of one workable rather than merely cheaper.

All six jobs

Get your listings online, and keep them current

Properties, stock, a team page, a directory, a menu. The content changes every week, and the website should not need a developer every week. Records holds entries of a shape you define once.

Decide the shape once

Set the fields a listing has: price, address, availability. Every entry then has the same shape and nothing gets left out.

Records

Anyone on staff can update it

Add and edit entries in the panel like filling in a form, or ask an agent to do it. Nothing is public until someone publishes it.

Records

The site shows what you published

Your website reads the published entries directly. Changing a price does not mean rebuilding the site.

Records · Cloud

Photos come from your drive

Attach them from the same shared drive the rest of the business uses, shared by link.

Drive

All six jobs

Hire someone, without buying a hiring tool

A hire is a project with a deadline, a pile of documents, and a small group of people allowed to read them. That is four subscriptions you were about to start.

Write the role, then publish it

Draft it with the team, then put it on your own careers page as a listing.

Documents · Records · Cloud

Applicants in one shape

Every candidate is an entry with the same fields, not a thread in someone’s inbox. An agent puts them in that shape as they arrive.

Records

Interviews booked, notes kept

The write-up sits next to the candidate instead of in someone’s head.

Calendar · Documents

Only the panel sees it

Applications are visible to the hiring group and nobody else. One decision, not a permission per file.

Groups

All six jobs

Build the intranet you never got round to

Every company has one in a shared folder somewhere, half written, three years old. It never gets finished because it needs four different kinds of thing in one place.

A handbook that is actually current

Policies and how-we-do-things as documents people read, updated in the conversation that changed them.

Documents

The lists that are really tables

Contacts, equipment, suppliers, who holds which key. Structured entries, not a spreadsheet emailed around.

Records

Files where people look for them

A shared drive that mounts like any other, reachable from a desk or from a job.

Drive

Inside only, by default

It sits inside your organisation, and if you host a page for it, behind your own login.

Groups · Cloud

All six jobs

Put an idea in front of people

You want to show a concept, not commission a project. A page, a prototype, something real enough that people can react to it, before anyone has decided it is worth building properly.

Describe it, don’t build it

Say what the idea is and who it is for. An agent writes the site and puts it up; you approve the change, not the configuration.

Concierge · Cloud

On a real address

It goes live somewhere you can send to someone. Bring a domain you already have, or take one here.

Cloud

Show it to a few people first

Put your own login in front of it, so only the people you invite see it while it is still an idea.

Cloud · routes

Change it while they are watching

Ask for a change and see it live. If yesterday’s version was better, go back to it.

Concierge · Cloud

All six jobs

Ship software without running a platform team

You write code, and you would rather not run a platform team to get it in front of anyone. Two of the platform’s pieces carry this on their own: Forge and Cloud.

Forge

Git hosting inside the platform: branches, reviews, merges and access tokens, over the standard git protocol at git.dirb.ai. No lock-in.

Forge

A development environment in the cloud

Bring up a dev pod to debug or run software, with a database beside it. It cannot be published: routes are refused there, so a sandbox never turns into public traffic.

Cloud · development

Build, then serve

Point at a repo and a Dockerfile, get a versioned image in your own private registry, then run services, stateful sets and jobs in isolated namespaces.

Cloud · build · serving

Secrets injected, never handled

Workloads get the org secrets they need at run time, injected straight from your vault. The platform never handles the values itself.

Vault · Cloud

Your own login in front of it

Put your own OIDC provider in front of a hosted site, so visitors sign in with your identity provider rather than ours.

Cloud · routes

An agent that writes the infrastructure

Environments, services, routes and domains are declared in your own git repository. An agent authors that config the way it authors application code, through a pull request you review.

Forge · Cloud

All six jobs

Start with the one you came for

Request early access. When you are in, your first three seats are free, and one of them can be an agent.

Built by a small team that runs their own business on it.

Request Early Access Back to the overview

Early access is invite-gated: requesting opens the sign-up on panel.dirb.ai. Free to start once you are in, no credit card.