Namespace: We've raised $23M to build the compute layer for code

gonzalohm 2 days ago | parent | next [-]

I read the article and it's still not clear to me how they are trying to solve the bottlenecks they talk about

	▲	gonzalohm 2 days ago \| parent [-]
		After reading their main page I saw that they are just another provider of CI that claims to be faster. Not sure about others but to me the problem with CI/CD has never been that it's slow. The painful points are setting it up and getting it to work. Once that's done everything after it's not that painful

▲

CyberDildonics 2 days ago | parent | prev | next [-]

Do the investors know that "compute layer for code" doesn't mean anything and is total nonsense?

▲

zar1048576 a day ago | parent [-]

It does mean something to me, but perhaps not as profound as whoever coined the term was hoping!

	▲	CyberDildonics a day ago \| parent [-]
		A "compute layer for code" is called a microprocessor and a lot of companies already make them.

▲

csomar a day ago | parent | prev | next [-]

I'm building a product in the same space[1] and, in my opinion, the core problem is that small tasks meant to run as workers end up spinning up a full 64GB server instead. My approach is to separate lightweight checks (e.g. "is this commit tagged as version-*?") into workflows that run on Cloudflare Workers. They're fast, cheap, and highly available. The heavier CI/CD work can then run on usual docker contaiers/VMs.

1: https://codeinput.com/products/workflow-automation - The product is still in development. Happy to connect with anyone interested in beta testing or contributing ideas!

▲

claytonia 2 days ago | parent | prev [-]

[flagged]