Directory is a lightweight directory of developer-focused platform tools (PaaS, DaaS, hosting platforms, CI/CD, managed services, etc.). It helps developers, teams, and decision-makers discover, compare, and pick tools by exposing key features, pricing signals, and suitability based on user preferences such as budget, coding experience, and deployment needs.
Key goals
- Centralize information about developer platforms and hosting tools.
- Provide side-by-side comparisons of features and pricing.
- Help users filter and choose tools based on preferences (price, experience level, runtime/language support, scale, managed vs self-hosted).
Main capabilities
- Browse curated entries for platform tools (each entry includes short summary, features, pricing notes, and suitability tags).
- Compare multiple tools on feature sets and price-related attributes.
- Filter/search by categories (PaaS, DaaS, hosting, DB-as-a-Service, serverless, container hosting) and by preference (budget, developer experience, language/runtime).
- Lightweight UI and data-first structure so content can be extended easily.
Quick start (developer)
- Clone the repo: git clone
- Install dependencies:
- JavaScript/Node: npm install (or yarn)
- Python: pip install -r requirements.txt
- (Adjust depending on repo language)
- Run locally:
- For Node/React apps: npm start
- For static sites: serve or open index.html
- For backend services: follow specific service README or run with the configured environment variables
- Add or edit tool entries:
- Tool data is stored in /data, /tools, or a similar directory (JSON / YAML / DB). Add a new entry with required fields: name, category, short_description, features[], pricing, tags[].
How to choose a tool (user guidance)
- If you want the simplest developer experience with minimal ops: prefer "Managed PaaS" or "Serverless" tags.
- If you need fine-grained control and lower long-term cost: consider container hosts or self-hosted options.
- For budget constraints: filter by pricing and look for free tiers or pay-as-you-go.
- For language/runtime support: filter by supported runtimes listed in each tool entry.
Contributing
- Add new tool entries or improve existing ones (follow the data schema in /data or check the sample entry).
- Improve comparison logic, add more filters, or enhance the UI for clarity.
- Submit pull requests and include tests or screenshots for UI changes.
Data & Schema
- Each tool entry should include at minimum:
- id, name, category, summary, features (array), pricing_summary, supported_runtimes (array), ideal_for (tags), official_url
- Keep entries factual and link to official docs for pricing or feature confirmations.
Limitations & Notes
- Pricing summaries are indicative — always follow the vendor’s pricing pages for exact quotes.
- Tool suitability is an opinionated recommendation; validate with your team's constraints before adopting.
License
- Add a LICENSE file in the repo (e.g., MIT) or follow the repository’s existing license.
Contact / Maintainer
- Repository owner: @samlan24
- Open issues or PRs for corrections, new tools, or feature requests.