Application framework for Go
Build Go applications,
not boilerplate
Develop standalone and web applications faster for modern Go projects.
package main import ( "os" "codnect.io/procyon") func main() { if err := procyon.Run(); err != nil { os.Exit(1) } }Why Procyon
Procyon makes programming Go applications quicker, clearer, and easier to grow with a runtime focused on structure, simplicity, and productivity.
Easy to use
Start with familiar Go code and grow into web, CLI, or background applications without learning a separate programming style.
Boilerplate free
Let Procyon handle common application wiring so more of your time goes into the behavior your product actually needs.
Fast
Keep startup, shutdown, and feedback loops quick with a runtime that adds structure without slowing the application down.
Structured
Organize controllers, services, and shared dependencies as components so the application remains readable as it grows.
Configurable
Bind environment values, config files, profiles, and property sources through one predictable configuration model.
Extensible
Add HTTP, components, configuration, lifecycle, and CLI support as focused packages that fit the same runtime.
Runtime in practice
See how a Procyon app comes together
Create a handler, connect it to routes, turn it into a component when it needs dependencies, then start the application runtime.
type WelcomeHandler struct {}Â func NewWelcomeHandler() *WelcomeHandler { return &WelcomeHandler{}}Â func (w *WelcomeHandler) hello(ctx http.Context) error { return ctx.String("Hello from Procyon")}Get started
Build your first Procyon application
Start with the quick start, then add components, configuration, HTTP routes, or CLI commands as your application grows.
Comparison
Compared with Go frameworks
Gin, Echo, and Fiber are strong choices for HTTP. Procyon fits when the whole application needs a shared runtime shape.
Latest news
Updates from Procyon
Framework notes, design decisions, and release context as the application runtime grows.
Why application structure matters in Go
How configuration, components, lifecycle, and startup fit together when a Go application grows beyond a small handler.
Read updateDesigning component registration that stays readable
Keeping dependencies explicit while giving controllers, services, configuration, and infrastructure components a clear place to live.
Read updateSmall entrypoints, clear runtime signals
Useful startup signals, predictable lifecycle phases, and less ceremony in application code.
Read updateFAQ
Common questions
A few practical answers about where Procyon fits, what it replaces, and when it becomes useful in a Go application.
Why does Procyon exist when Go already has many frameworks?+
Many Go frameworks focus mainly on HTTP routing. Procyon aims to be an application framework: it brings components, dependency injection, configuration, lifecycle, CLI, and HTTP support into one runtime model so larger applications have a predictable structure.
Is Procyon only for web applications?+
No. Procyon is designed for web services, command-line tools, background workers, and standalone Go applications that need a clean startup model and shared runtime features.
When should I use it?+
Use it when your project has multiple components, configuration sources, profiles, lifecycle hooks, or startup concerns that you want to keep organized without building that structure from scratch.
Discover more
Join the Codnect community
Follow the projects, share ideas, and help shape open source software for developer ecosystems