Start building on Google Cloud with $300 in free credits. No commitment, no credit card required until you're ready to scale.
Launch your next project with $300 in free Google Cloud credits—no strings attached. Test, build, and deploy without risk. Use your credits across the entire Google Cloud platform to find what works best for your needs. After your credits are used, continue with always-free tier services. Only pay when you're ready to scale. Sign up in minutes and start exploring.
Start Free Trial
Build Agents and Models on One Platform
Everything you need to build production-ready agents and models. Access 200+ Google and third-party AI models and tools.
Gemini Enterprise Agent Platform is Google Cloud's comprehensive platform for developers to build, scale, govern, and optimize agents and models. Choose from Google's most advanced models and third-party models like Anthropic's Claude Model Family.
A free and portable Common Lisp Webserver.
Portable AllegroServe is a variant of AllegroServe(tm) with an explicit emphasis on portability between Lispsystems and Operating Systems. You can find the original AllegroServe at https://github.com/franzinc/aserve
The best way to install Portable AllegroServe is through Quicklisp (http://quicklisp.org/). (The best way to install any Lisp library is through Quicklisp.)
3store is an RDF "triple store", written in C and backed by MySQL and Berkeley DB. It is an optimisation and port of an older triple store (WebKBC). It provides access to the RDF data via RDQL or SPARQL over HTTP, on the command line or via a C API.
Lisplets are Java Servlets that forward their requests, and gather their response headers, using s-expressions over sockets. They enable easy integration of Common Lisp or Scheme into a Java-based web environment.
The Lavlet HTTP server and Lisp Server Pages engine is a complete ANSI Common Lisp web server and dynamic pages engine for Lisp modeled after JSP/Servlet/Tomcat and ASP/IIS.
AppSignal's MCP server hands Claude, Cursor, or Zed your real errors, traces, and the deploy that shipped them. AI writes the fix; you review the diff.