theincyber/mike

A privacy-minded take on Mike that keeps a firm's AI traffic inside its own Microsoft Azure tenant.

Early days - a single thread of work and not much divergence yet, with a recent push suggesting theincyber is still poking at it.

View on GitHub →

This is theincyber's fork of Mike, aimed at firms that want the assistant but not the data-handling questions that come with sending model traffic straight to OpenAI. The one direction visible so far is a way to route Mike's AI calls through a customer's existing Azure account, so the model usage stays inside infrastructure the firm already controls and trusts.

We don't have much else to go on yet about who theincyber is beyond the handle. The work that's tracked is a single, coherent idea rather than a broad rebuild, and there's no rebrand or niche repositioning on display - it still reads as Mike, with a deployment story bolted on for security-conscious shops.

If you run a practice that already lives in the Microsoft cloud and cares where your prompts go, this is the fork worth watching. Click through to GitHub if you want to see how far along the Azure plumbing actually is.

What's in it

Direction

integrationinfrastructuresecurity

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

Threads of work (detailed view)

1 thread have been distilled into posts.

Pull requests (detailed view)

1 PR touch this fork — inbound (filed against it) or outbound (filed from it). State icons match the editorial dashboard.

🟢 Open (1)