// questions
Questions, answered.
Short answers to the things people ask before they trust us with their demo. Missing one? hi@uglytool.dev.
Why do I need this?
Your model works. Your demo does not read like a product. That's the gap we close. Three finished looks. Pick one, drop it in. Your work stays yours.
// same tool, two shells. left is the live HF Space in its default Gradio theme; right is the same tool previewed in After Hours — the look we'd sell you.
Do you look at my code?+
No. Never. Even the HF URL path only reads the public
/config JSON that your tool's browser already reads — component layout, field labels, nothing else. Your source code stays wherever you keep it.What am I actually buying?+
A look for your tool — two clean files (an HTML shell and a CSS theme) in one of our three finished looks: After Hours, Vellum, Clean Room. Use the HTML as a standalone front-facing page, drop the CSS into your existing app, or both. Your logic stays yours.
How complex is the integration? Can I see the steps before I buy?+
Yes. Two paths, both simple:
- Path A — drop-in CSS for Gradio or Streamlit. Upload one file, paste two short Python lines, commit. About five minutes.
- Path B— standalone HTML. Host on GitHub Pages, Vercel, or Netlify; point it at your backend's API.
Can I edit the files after I download them?+
Yes. They're yours. Break them, rebrand them, rewrite them, embed them in a Vue app — we don't care. They're starting points, not frameworks.
Will this work with Streamlit / Flask / FastAPI / my private Space?+
Yes. For Gradio and Streamlit, the CSS file drops in directly with two short lines of Python (Path A). For Flask, FastAPI, or anything else, host the HTML and point your framework at it (Path B). The README ships with short snippets for both. Private Spaces work via the description path instead of the URL path.
What if my tool isn't on Hugging Face?+
Use the description path — write a paragraph about your tool in plain language. The preview won't be pixel-identical to your UI (URL path reads your Gradio config; description is an approximation), but the look you buy is the same either way.
What happens to the text I paste in?+
It populates the copy in your preview — tool name, tagline, input labels, output labels, description block. That's it. We don't train on it, we don't keep it beyond rendering the preview.
Can I customize the colors or fonts?+
Not in v1. Three fixed palettes — that's the whole pitch. If you want infinite knobs, you're back to building your own look, which is what you're here to avoid. Seasonal drops add new looks periodically and are sold separately.
Why does my button say "Execute" when my tool says "Submit"?+
Because the look is talking. Your tool's content — name, description, field labels — carries through verbatim. The ornamental copy — button text, label casing, section names ("Parameters" / "Findings" / "Results") — comes from the look's voice. That's the point: three distinct personalities, each speaking its own dialect. If you want your button to say “Submit,” open the file and change one word. It's yours now.
I'm stuck dropping this into my tool. Help?+
Throw the README + the files at whichever LLM you're already talking to. They know your framework better than we do — we just stop things from being ugly. Every purchase ships with a
README.md covering drop-in snippets for Gradio, Streamlit, Flask, and plain static sites.How do I pay?+
Through Stripe. Pay with a card; you're unlocked instantly on the device you bought from, plus an emailed backup link for other devices. The pricing page shows the four SKUs: free preview, single look ($19), catalog pass ($39), seasonal drops ($9).
What are seasonal drops?+
Limited-time looks we release periodically — think a Christmas palette, a Halloween one, a Valentine's. One at a time, available during its window only, and only to catalog-pass holders at $9 each. Rare by design.