Submit your project¶
Built something with Promptise Foundry? We want to see it. We feature standout projects in our showcase, documentation, social channels, and community highlights. Submitting is free, open to everyone, and takes 5 minutes.
What we're looking for¶
We feature projects that demonstrate real use of Promptise Foundry — not wrappers around build_agent() with default settings, but systems that solve actual problems for real users or push the framework in directions we did not anticipate.
Strong submissions typically have:
- A working deployment or demo (not just a repo with a README)
- Clear use of at least one Promptise module (Agent, MCP Server, Runtime, Prompts, Context Engine)
- A problem statement — what does this solve, and for whom?
- Something we can link to — a live product, a public repo, a demo video, or a detailed write-up
We are especially interested in:
- Production systems handling real traffic
- Novel MCP server implementations (new tool domains, creative integrations)
- Agent Runtime deployments with governance (budget, health, mission)
- Multi-agent systems with meaningful coordination
- Prompt engineering patterns that measurably improved output quality
- Open-source tools that extend the Promptise ecosystem
- Industry-specific applications (healthcare, finance, legal, education, DevOps)
Submission requirements¶
Your submission must include all of the following:
| Field | Required | Description |
|---|---|---|
| Project name | Yes | A clear, descriptive name |
| Your name or team | Yes | Who built it |
| Contact email | Yes | For follow-up questions only — never shared publicly |
| Project URL | Yes | Live product, GitHub repo, demo video, or detailed blog post |
| One-paragraph description | Yes | What it does, who it serves, what problem it solves (max 200 words) |
| Promptise modules used | Yes | Which pillars: Agent, MCP Server, Runtime, Prompts, Context Engine |
| Key features | Yes | 3-5 bullet points of what makes this project notable |
| Screenshot or architecture diagram | Recommended | Visual context helps reviewers understand your system faster |
| Metrics or impact | Recommended | Users served, queries handled, cost savings, uptime — anything quantifiable |
| Open source? | Yes | If yes, link to the repo. If no, that is fine — commercial projects are welcome |
| License | If open source | MIT, Apache 2.0, etc. |
What happens after you submit¶
- We review every submission. There is no automated filter. A human reads your submission and evaluates it.
- Review takes up to 14 days. We batch reviews. If we need more information, we will email you.
- Accepted projects get featured. Where depends on the project — showcase page, social media, documentation examples, or community highlights.
- We may reach out for a deeper feature. Exceptional projects may be invited for a case study, blog post, or co-marketing opportunity.
Review criteria¶
We evaluate submissions on five dimensions. You do not need to score high on all five — a project that excels in one area can still be featured.
| Criterion | What we look for |
|---|---|
| Usefulness | Does this solve a real problem? Would other developers or businesses benefit from seeing this? |
| Technical depth | Does it use Promptise features beyond the basics? Multi-module integration, governance, custom stores, creative MCP servers? |
| Quality | Is the code clean? Is the deployment reliable? Does the README explain how to run it? |
| Originality | Does this show something new? A use case we had not considered, a pattern that surprised us? |
| Completeness | Is it finished enough to be useful? We do not feature half-built prototypes unless the concept is exceptional. |
What we do NOT feature¶
To keep the quality bar high, we decline submissions that:
- Are tutorials or learning exercises with no real-world application
- Only use
build_agent()with default parameters and no meaningful integration - Are clones of our existing examples with minor modifications
- Contain placeholder data, fake demos, or non-functional deployments
- Violate any third-party terms of service, privacy laws, or ethical guidelines
- Are primarily marketing vehicles for unrelated products
We reserve the right to decline any submission without providing a reason. This is not a reflection of your work — our showcase has limited space and we prioritize diversity of use cases, industries, and technical approaches.
How to submit¶
Send an email to showcase@promptise.com with the subject line:
Include all required fields from the table above in the email body. Attach screenshots or diagrams as image files (PNG, JPG) or link to them.
Alternatively, open a GitHub Discussion in the Promptise Foundry repository under the Show and Tell category with the same information.
Featured project benefits¶
Projects that are accepted receive:
- Showcase listing — your project on our What You Can Build page with description, link, and screenshot
- Social promotion — featured on Promptise social channels (LinkedIn, Twitter/X)
- Documentation reference — exceptional projects may be cited as examples in our technical docs
- Community recognition — a "Featured Project" badge for your repo (if open source)
- Direct line to the team — featured project maintainers get priority access to our team for technical questions and early feature previews
Updating or removing your project¶
If your project changes significantly (new features, new URL, new name), email us with the updated information and we will refresh your listing.
If you want your project removed from the showcase, email us and we will remove it within 48 hours. No questions asked.
Questions?¶
If you are unsure whether your project qualifies, submit it anyway. The worst that happens is we say no. The best that happens is we feature it and thousands of developers see your work.
For questions about the submission process, email showcase@promptise.com.