Add Generative AI Companies

[AlexChalakov]

https://github.com/AlexChalakov/awesome-generative-ai-companies

It is a thoroughly researched list of companies that indulge in Generative AI with over $5MM raised as of August 2023. It is useful for the following few reasons:

• People would be able to keep informed regarding new intriguing and exciting Generative AI projects.
• People would be able to "job hunt" through this list and see if there is a company that matches their interests.
• The Industry is evolving and changing rapidly, so it would be useful to have somewhere where all of those companies could be monitored and listed.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.

• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.

• You have to review at least 2 other open pull requests.
  Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.

• Add Frontend GIS #2731 (comment)

• Add Astrophysics Simulation Codes #2737 (comment)

• You have read and understood the instructions for creating a list.

• This pull request has a title in the format Add Name of List. It should not contain the word Awesome.

  • ✅ Add Swift
  • ✅ Add Software Architecture
  • ❌ Update readme.md
  • ❌ Add Awesome Swift
  • ❌ Add swift
  • ❌ add Swift
  • ❌ Adding Swift
  • ❌ Added Swift

• Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

  • ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
  • ✅ - [Framer](…) - Prototyping interactive UI designs.
  • ❌ - [iOS](…) - Resources and tools for iOS development.
  • ❌ - [Framer](…)
  • ❌ - [Framer](…) - prototyping interactive UI designs

• Your entry should be added at the bottom of the appropriate category.

• The title of your entry should be title-cased and the URL to your list should end in #readme.

  • Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

• No blockchain-related lists.

• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• Has been around for at least 30 days.
  That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
• Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
• The default branch should be named main, not master.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
  • ✅ Mobile operating system for Apple phones and tablets.
  • ✅ Prototyping interactive UI designs.
  • ❌ Resources and tools for iOS development.
  • ❌ Awesome Framer packages and tools.
• It's the result of hard work and the best I could possibly produce.
  If you have not put in considerable effort into your list, your pull request will be immediately closed.
• The repo name of your list should be in lowercase slug format: awesome-name-of-list.
  • ✅ awesome-swift
  • ✅ awesome-web-typography
  • ❌ awesome-Swift
  • ❌ AwesomeWebTypography
• The heading title of your list should be in title case format: # Awesome Name of List.
  • ✅ # Awesome Swift
  • ✅ # Awesome Web Typography
  • ❌ # awesome-swift
  • ❌ # AwesomeSwift
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate. Please search for existing submissions.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
• Includes a project logo/illustration whenever possible.
  • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
  • The image should link to the project website or any relevant website.
  • The image should be high-DPI. Set it to maximum half the width of the original image.
• Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
• Includes the Awesome badge.
  • Should be placed on the right side of the readme heading.
    • Can be placed centered if the list has a centered graphics header.
  • Should link back to this list.
• Has a Table of Contents section.
  • Should be named Contents, not Table of Contents.
  • Should be the first section in the list.
  • Should only have one level of nested lists, preferably none.
  • Must not feature Contributing or Footnotes sections.
• Has an appropriate license.
  • We strongly recommend the CC0 license, but any Creative Commons license will work.
    • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
  • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
  • Place a file named license or LICENSE in the repo root with the license text.
  • Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
  • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
• Has contribution guidelines.
  • The file should be named contributing.md. Casing is up to you.
  • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
  • The section should not appear in the Table of Contents.
• All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
• Has consistent formatting and proper spelling/grammar.
  • The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
  • The description starts with an uppercase character and ends with a period.
  • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• Does not use hard-wrapping.
• Does not include a CI (e.g. GitHub Actions) badge.
  You can still use a CI for linting, but the badge has no value in the readme.
• Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

[AlexChalakov]

unicorn

[donBarbos]

i checked the requirements including linter and lint is passing

➜  ~ npx awesome-lint https://github.com/AlexChalakov/awesome-generative-ai-companies
✔ Linting

But

1. you don't need to store the .DS_Store file in the repository
2. you use hard-wrapping in readme file from line 5 to 7 and check other markdown files hard-wrapping

[AlexChalakov]

i checked the requirements including linter and lint is passing

➜  ~ npx awesome-lint https://github.com/AlexChalakov/awesome-generative-ai-companies
✔ Linting

But

1. you don't need to store the .DS_Store file in the repository
2. you use hard-wrapping in readme file from line 5 to 7 and check other markdown files hard-wrapping

Both of those have now been fixed. Can't find any other hard wrapping in the other markdown files

[donBarbos]

I think it's worth re-reading what hard-wrapping is. I found a lot more hard-wrapping in your files.

Check all the lines yourself, here are just a few of them: readme.md - 194, 588, 635 lines, contributing.md - 3-5, 20-25 lines,
almost the entire code-of-conduct.md (although sindresorhus/awesome/code-of-conduct.md also has a lot of line transfers, so I think the main thing is that the readme shouldn't have)

Why are you quoting the description? In your case they have no value, it's better to do without them.
I also advise you to move the line Fundraised around ... according to ... to brackets so as not to spoil the list
from this:

- [Grammarly]() - "Digital writing assistant."

Fundraised $400M according to Crunchbase and DealRoom

make this:

- [Grammarly]() - Digital writing assistant, [$400M](Crunchbase link).
or
- [Grammarly]() - Digital writing assistant ([$400M](Crunchbase link)).

it also makes no sense to group by the amount of raised money, since they are arranged in ascending order anyway

[AlexChalakov]

I think it's worth re-reading what hard-wrapping is. I found a lot more hard-wrapping in your files.

Check all the lines yourself, here are just a few of them: readme.md - 194, 588, 635 lines, contributing.md - 3-5, 20-25 lines, almost the entire code-of-conduct.md (although sindresorhus/awesome/code-of-conduct.md also has a lot of line transfers, so I think the main thing is that the readme shouldn't have)

Why are you quoting the description? In your case they have no value, it's better to do without them. I also advise you to move the line Fundraised around ... according to ... to brackets so as not to spoil the list from this:

- [Grammarly]() - "Digital writing assistant."

Fundraised $400M according to Crunchbase and DealRoom

make this:

- [Grammarly]() - Digital writing assistant, [$400M](Crunchbase link).
or
- [Grammarly]() - Digital writing assistant ([$400M](Crunchbase link)).

it also makes no sense to group by the amount of raised money, since they are arranged in ascending order anyway

Thank you for the feedback. I will go through all of the files and check for hard wrapping again. I have to say the the code-of-conduct.md file does not necessarily fall under this, since it is copy and pasted from sindresorhus's repository.

Regarding the other comments, I can't say I really agree with them. I find value in quoting the descriptions of the company because those descriptions are directly taken from their websites/social media profiles/other pages, so it is not my thought or saying, but rather their own description of who they are. I think this is better presenting someone else's thoughts and does not put liability on me in case something is wrong.

Regarding the format of the list, it consists of hundreds of companies and is increasing by the minute, so except mandatory, I would refrain from switching its format and would just leave the 'Fundraised around ... according to ...' part.

Finally, at least to me it makes sense for the companies to be grouped by the amount of raised money. Those are important thresholds and I believe it's vital for some people to be able to select just the right category they want to go through. It's cleaner and more organised this way.

[donBarbos]

there is a specific requirement in pull_request_template.md:

The description starts with an uppercase character and ends with a period.

you have a quote at the end of the line

Correct example:

- [AVA](…) - JavaScript test runner.

[sir-kokabi]

I would recommend not using quotation marks around the descriptions. It's a common convention to present descriptions in lists without them, and it can make the content appear cleaner and more streamlined.

I mean, instead of this::

Replika - "Developing digital copy of the human in the form of a chat-bot."

use this:

Replika - Developing digital copy of the human in the form of a chat-bot.

[sindresorhus]

Bump

[yackermann]

LGTM

[kuhel]

Seems legit

[ggbetz]

Hi! Very interesting and helpful list. My suggestion: add together.ai.