Behold the continued tradition of AI products having logos that look like buttholes.
Mike: open-source legal AI
51–60 of 123 posts
Re: Mike: open-source legal AI
#52Because using LLMs for legal work has never gone wrong, and LLMs have never cited completely hallucinated cases
Re: Mike: open-source legal AI
#53This website is actually gorgeous. What do you call this style?
Do you just mean the Monet at the top? I know little about art, but I assume impressionism.
That, plus an Anthropic-like logo.
Re: Mike: open-source legal AI
#54I'm a little puzzled by what this actually is supposed to be. The marketing material on this website suggests that it's meant to be used with a firm's Gemini or Claude API keys. ("A chat interface that reads your documents, cites verbatim, runs multi-step workflows, and drafts and edits contracts end-to-end. Plug in your own Claude or Gemini keys, and keep full control of the models you use.").
If that's true, how does it actually achieve anything with respect to client confidentiality or anything else? (For example, there's the claim "the assistant keeps full context across every conversation and every document." --- but isn't that a function of the model one uses, which is on Anthropic or Google? Ditto the claim "Documents never leave your perimeter. Compliance, residency, and privilege stay under your control." But this is only true if you're not piping them to Anthropic or Google...) Is this just a user interface?
It would be nice if these product webpages included an easy way to find documentation so that one could figure out what the product actually does. I can't find any obvious way to discern if it can be easily used with a local model running via ollama or something, for e.g.
Re: Mike: open-source legal AI
#55I believe this is the direction enterprise software is generally going. An open-source base with a very permissive license that then each company can adapt (with claude, codex, etc.) for it's own needs. It's either running it on it's own infrastructure or in hosted environment by the author. I've built a similarly extensible codebase for an ERP: https://github.com/lambdadevelopment/lambda-erp
How will developers of this software get paid in this model?
Re: Mike: open-source legal AI
#56I find the name and presentation well chosen. For whatever reason "Mike" fits well in this legal context.
Re: Mike: open-source legal AI
#57I'm a little puzzled by what this actually is supposed to be. The marketing material on this website suggests that it's meant to be used with a firm's Gemini or Claude API keys. ("A chat interface that reads your documents, cites verbatim, runs multi-step workflows, and drafts and edits contracts end-to-end. Plug in your own Claude or Gemini keys, and keep full control of the models you use."). If that's true, how do…
These firms have enterprise relationships that dictate all of that. This is presumably just a frontend that takes the key as an input and plugs into that infrastructure.
Re: Mike: open-source legal AI
#58I'm a little puzzled by what this actually is supposed to be. The marketing material on this website suggests that it's meant to be used with a firm's Gemini or Claude API keys. ("A chat interface that reads your documents, cites verbatim, runs multi-step workflows, and drafts and edits contracts end-to-end. Plug in your own Claude or Gemini keys, and keep full control of the models you use."). If that's true, how do…
The "open source" part is the wrapper on top (up to you if you believe that's meaningful here)
Re: Mike: open-source legal AI
#59I believe this is the direction enterprise software is generally going. An open-source base with a very permissive license that then each company can adapt (with claude, codex, etc.) for it's own needs. It's either running it on it's own infrastructure or in hosted environment by the author. I've built a similarly extensible codebase for an ERP: https://github.com/lambdadevelopment/lambda-erp
How will developers of this software get paid in this model?
[deleted]
Re: Mike: open-source legal AI
#60I believe this is the direction enterprise software is generally going. An open-source base with a very permissive license that then each company can adapt (with claude, codex, etc.) for it's own needs. It's either running it on it's own infrastructure or in hosted environment by the author. I've built a similarly extensible codebase for an ERP: https://github.com/lambdadevelopment/lambda-erp
I'm really interested in how LLMs will enable more customizable, personal software. Our PMs & Designers are writing a lot of code now, and our engineers are spending time figuring out how to make a system that's easy for PMs & designers to extend/add to.
It's not a big leap to apply that model to a company and its customers, where the company builds a well-abstracted, easily extensible base that 1) Customers can easily extend/customize for their workflows 2) Customers can self-host or run fully isolated, much easier (probably not quite there yet, but is a possible world)