Hugging Face
Search models, datasets, users...
Ctrl K
Models
Datasets
Spaces
Buckets
Docs
Enterprise
Pricing
Website
Tasks
HuggingChat
Collections
Languages
Organizations
Community
Blog
Posts
Daily Papers
Hardware
Learn
Discord
Forum
GitHub
Solutions
Team & Enterprise
Hugging Face PRO
Enterprise Support
Inference Providers
Inference Endpoints
Storage Buckets
Log In
Sign Up
Spaces:
Vebera
/
cloudsaas-control-hub
Like
0
Running
App
Files
Files
Community
main
cloudsaas-control-hub
89 kB
Ctrl+K
Ctrl+K
1 contributor
History:
5 commits
Vebera
copy colors from https:/qate.app
db7cdce
verified
about 1 year ago
.gitattributes
Safe
1.52 kB
initial commit
about 1 year ago
README.md
Safe
247 Bytes
Build a cloud service control (SaaS) application with the cabinet, payment integration, dashboard with the API / token use statistics, take examples from openrouter.com, cloud.qdrant.com, it must support light and dark mode. Each component has its own file. The Front-end site shall have access to REST API of the server. The billing area of the backend should offer several product packages: each shall include a certain amount of test runs (computing power), number of users and AI agent support. The very basic tariff would anticipate 1000 test runs to consume in a period of 3 months, for instance. The site must also have T&C and all required policies for the user to accept. The dashboard would show the limit consumption,
about 1 year ago
api-keys.html
Safe
13.5 kB
it has 2 avatars in the toolbar - not good
about 1 year ago
billing.html
Safe
16.7 kB
API Keys and dashboard must be seen after sign-in - in the user profile.
about 1 year ago
dashboard.html
Safe
15.5 kB
Build a cloud service control (SaaS) application with the cabinet, payment integration, dashboard with the API / token use statistics, take examples from openrouter.com, cloud.qdrant.com, it must support light and dark mode. Each component has its own file. The Front-end site shall have access to REST API of the server. The billing area of the backend should offer several product packages: each shall include a certain amount of test runs (computing power), number of users and AI agent support. The very basic tariff would anticipate 1000 test runs to consume in a period of 3 months, for instance. The site must also have T&C and all required policies for the user to accept. The dashboard would show the limit consumption,
about 1 year ago
index.html
Safe
14.2 kB
copy colors from https:/qate.app
about 1 year ago
profile.html
Safe
10.6 kB
API Keys and dashboard must be seen after sign-in - in the user profile.
about 1 year ago
signin.html
Safe
8.23 kB
API Keys and dashboard must be seen after sign-in - in the user profile.
about 1 year ago
signup.html
Safe
8.09 kB
API Keys and dashboard must be seen after sign-in - in the user profile.
about 1 year ago
style.css
Safe
388 Bytes
initial commit
about 1 year ago